Matthew Burgess wrote: > I'm hoping the dev.d scripts are all handled asynchrohously - i.e. > udev doesn't wait for one to complete before kicking off the next, > otherwise boot times might be significantly slowed down with all that > spinning.
Uh oh. ;-) udev-056 does indeed wait for each of the dev.d handlers to finish before starting the next one. This is handled inside run_program in udev_multiplex.c. (Both udev and udevstart call the udev_multiplex_directory function in that file, which calls run_program.) run_program forks, execs the handler in the child, and has the parent wait for it. However, I think the 1-second wait will probably be the worst case -- I don't think it'll spin around that loop more than once (if it does at all). Even the one-second wait could be reduced if there was a program that used directory-change notifications (inotify? maybe...) to sleep until a directory or file was created or modified, but I don't know of any such program. I'm fairly sure nothing like that is installed on a base LFS system.
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
