lp://staging/~jamesodhunt/upstart/kmsg-noctty
Created by
James Hunt
and last modified
- Get this branch:
- bzr branch lp://staging/~jamesodhunt/upstart/kmsg-noctty
Only
James Hunt
can upload to this branch. If you are
James Hunt
please log in for upload directions.
Branch merges
Propose for merging
No branches
dependent on this one.
- Stéphane Graber (community): Approve
-
Diff: 76 lines (+37/-14)2 files modifiedChangeLog (+6/-0)
init/main.c (+31/-14)
Related bugs
Bug #1263738: login console 0 in user namespace container is not configured right | Undecided | Fix Released |
Related blueprints
Branch information
Recent revisions
- 1592. By James Hunt
-
* init/main.c: logger_kmsg(): Use open(2) rather than fopen(3) to avoid
stealing the console in an container: fopen(3) may not specify
O_NOCTTY and Upstart should not own the console (LP: #1263738). - 1589. By James Hunt
-
* init/man/init.5: Explain valid syntax for stanzas
accepting a signal (such as 'kill signal'). - 1586. By James Hunt
-
* init/man/init.5: Comma-separate and sort SEE ALSO entries.
* init/man/init.8: Expand SEE ALSO section (debian bug#732128). - 1585. By James Hunt
-
* init/man/init.8:
- Refer to job goals in start/stop/restart commands.
- Explain actual semantics of restart (debian bug#732126). - 1584. By James Hunt
-
* init/man/init.5: Provide additional detail on start/stop on stanzas
with respect to how Upstart deals with complex conditions containing
multiple events (debian bug#732122).
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/upstart