Designing a new init: low level communication

a-aa a-aa at
Mon Aug 29 14:43:15 UTC 2005

Erich Schubert wrote:

>>You can pretty much keep trying to open /dev/unix_socket after execution
>>of each script until it works, it'll add a TINY bit of overhead, but..
>>not much really, trying to open it 1-5-10 times wont really make much
>Won't the unix socket be hidden by udev mounting a tmpfs over /dev?
>In that case either init must do some busy spinning, too, or we need
>to have udev signal init to recreate its socket.
The way initng does this is by trying to open /dev/initng/initng until
it works, and keep stat'ing it after executing of every script to make
sure it's in the live filesystem.

A single stat after every script is a tiny tiny bit of overhead, and
even so it should never have to recreate it, as it'll fail before udev
is mounted, as it would be on a read only filesystem at that point.

>best regards,
>Erich Schubert
>    erich@(|      --      GPG Key ID: 4B3A135C    (o_
>  To understand recursion you first need to understand recursion.   //\
>  Wo befreundete Wege zusammenlaufen, da sieht die ganze Welt für   V_/_
>        eine Stunde wie eine Heimat aus. --- Herrmann Hesse
>initscripts-ng-devel mailing list
>initscripts-ng-devel at

More information about the initscripts-ng-devel mailing list