Anonymous | Login | Signup for a new account | 11-10-2008 10:41 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000119 | [BusyBox] New Features | feature | always | 02-22-05 09:57 | 07-18-05 15:26 | ||||
Reporter | jfb2 | View Status | public | ||||||
Assigned To | BusyBox | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 1.00 | ||||||
Summary | 0000119: Allow signal to restart init | ||||||||
Description |
The init applet will restart (re-exec) itsself when it receives a SIGHUP. However, just before it enters its main loop, it resets SIGHUP to either re-load the inittab (or ignore it if no inittab is used). Thus preventing the re-exec option from being triggerable. This patch adds a signal handler for SIGQUIT for init that always causes init to re-exec itsself (along with killing anything else that might be still running). |
||||||||
Additional Information |
You may be asking why just reloading inittab was good enough. This patch was created for use when the system's root is changed (with pivot_root). After the new root FS in in play, all the old processes need to be terminated and we need to also stop the old init and restart it in the new root FS. |
||||||||
Attached Files | bb-restart.patch [^] (1,204 bytes) 02-22-05 09:57 | ||||||||
|
Copyright © 2000 - 2006 Mantis Group |