| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Don't directly execute bash for single-user mode, as that has SELinux ↵ | Bill Nottingham | 2010-06-29 | 1 | -1/+3 |
| | | | | | | | | | | | | issues. (#540216, #584443, #585053) If upstart directly runs bash for single-user mode, there's no way for SELinux to set the proper context (to distinguish it from other init scripts). Inserting a helper binary in the way allows for this. While we're changing this, we make it configurable so it's easily possible for people to use sulogin if they so desire. | ||||
| * | Fix debugging leftovers. | Bill Nottingham | 2010-05-19 | 1 | -2/+1 |
| | | |||||
| * | Improve shutdown splash screen reliability | Ray Strode | 2010-05-19 | 3 | -14/+28 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Right now the splash screen and rc script are racing with each other so you occasionally see a few shutdown messages before plymouth is up. This commit ensures proper synchronization between prefdm, plymouthd, and the rc script. It does this by 1) fully stopping prefdm before letting rc start 2) fully starting plymouth before letting rc start 3) if prefdm is running (e.g. runlevel 5), waiting until it is fully stopped before starting plymouthd 4) if prefdm is not running (e.g. runlevel 3), starting plymouthd right away One bit of complication in this commit is the "splash manager". It's a layer of indirection needed to handle the conditional mentioned in 3) and 4). There's no way within an upstart job file to say "start after the prefdm "stopped" event only if prefdm is not already stopped". We really need this to effectively happen, though, because if prefdm isn't in the process of stopping (because it was never started in the first place), it will never emit the stopped event and blocking for an event that never comes mean shutdown would never start. The splash manager checks if prefdm is already running and uses that information to emit an appropriate event that the plymouth-shutdown job can key of off. Note, one implication of 4) is we are showing plymouth when shutting down from runlevel 3 now. This is a change in behavior, but makes sense, since we show plymouth when starting up into runlevel 3. | ||||
| * | rcS*.conf - check if /etc/inittab exists (#590703) | Petr Lautrbach | 2010-05-13 | 2 | -2/+2 |
| | | |||||
| * | Fix shutdown as well as plymouth quitting. | Bill Nottingham | 2010-05-03 | 1 | -0/+1 |
| | | |||||
| * | Use 'task' for stopping plymouth. (<rstrode@redhat.com>) | Bill Nottingham | 2010-04-26 | 1 | -0/+2 |
| | | |||||
| * | Don't HUP init when messagebus starts (#557791) | Bill Nottingham | 2010-01-22 | 1 | -4/+0 |
| | | | | | | It drops the event queue, breaking other events. We need to find a better way to do this. | ||||
| * | Respawn correctly. (#552324, <zing@fastmail.fm>) | Bill Nottingham | 2010-01-05 | 1 | -5/+1 |
| | | |||||
| * | reload-init.conf: reload init on started messagebus | Petr Lautrbach | 2010-01-04 | 1 | -0/+4 |
| | | |||||
| * | Fix path reference. | Bill Nottingham | 2009-12-04 | 1 | -1/+1 |
| | | |||||
| * | Fix start-ttys for the correct number of ttys, and for X-on-tty1. | Bill Nottingham | 2009-12-03 | 1 | -0/+2 |
| | | |||||
| * | Fix default number of ttys. | Bill Nottingham | 2009-12-03 | 1 | -1/+1 |
| | | |||||
| * | Remove the dirty dirty hack in favor of an 'and' clause. | Bill Nottingham | 2009-12-03 | 1 | -20/+3 |
| | | | | | (This better work now.) | ||||
| * | Actually commit new files. | Bill Nottingham | 2009-12-03 | 3 | -0/+36 |
| | | |||||
| * | Coalesce the multiple rcX and ttyX jobs into single files. | Bill Nottingham | 2009-12-03 | 19 | -291/+16 |
| | | | | | | | Adjust other jobs accordingly. Use a configuration parameter for what ttys to start. | ||||
| * | Move to new upstart job location and file extension. | Bill Nottingham | 2009-12-03 | 21 | -0/+422 |
 |
index : initscripts | |
| Mageia fork of Fedora's Init Scripts | Colin Guthrie [colin] |
| aboutsummaryrefslogtreecommitdiffstats |