[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    [BusyBox] SIGHUP re-exec broken
From:       Russ Dill <Russ.Dill () asu ! edu>
Date:       2003-11-26 2:46:56
[Download RAW message or body]

I just noticed this:

Patch from  Andrew Flegg:

    Here's a pretty crude patch to reload /etc/inittab when init receives a
    SIGHUP. The mailing list archives weren't entirely clear on whether or
    not it should already happen, but didn't appear to be.

    The patch:
       * Adds a new function, reload_signal() which just calls
	 parse_inittab() and run_actions(RESPAWN)

       * Before entering the while (1) loop set up SIGHUP to call
	 reload_signal()

       * Modify new_init_action to skip the action if the same command
	 already exists on the same terminal

    This last bit means that changing already running entries is a bit
    hairy as you can end up with, for example, two shells running on the
    same virtual console. However, for solely adding/removing entries this patch
    seems to work quite well.

which was committed July 22nd, 2003. It breaks:

Add in a new restart init target, triggered by SIGHUP.  Patch from
Russ Dill, with adjustments by me.
 -Erik

applied December 17th 2001. Given that the latter is far more useful
(allowing one to unmount the rootfs so that it can be reflashed) and was
applied a lot longer ago. I'm thinking the reload inittab one should be
reversed.

-- 
Russ Dill <Russ.Dill@asu.edu>

_______________________________________________
busybox mailing list
busybox@mail.busybox.net
http://codepoet.org/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]