Thierry Vignaud writes:
> Juan Quintela <quintela@xxxxxxxxxxxxxxxx> writes:
>
> > > BTW, Juan: I haven't yet received a followup about what was going
> > > wrong with your /lib/dev-state and /dev/log problems.
> >
> > I don't know really, I think that it was a devfsd package here that
> > got a wrong config file :(
>
> the /dev/log problem has been traced back to the following portion of
> /etc/rc.d/rc.sysinit :
>
>
> # Restart devfsd actions now that the filesystems are ready
> if [ -c /dev/.devfsd ]; then
> if [ -x /sbin/devfsd ]; then
> # cleanup dynamic desktop directories before calling devfsd actions
> rm -f /usr/share/gnome/desktop/* /usr/share/apps/kdesktop/Desktop/*
>
> action "Running devfsd actions: " killall -HUP devfsd
> fi
> fi
>
>
> sometimes, the bootstraping process wait for minutes because of some
> sort of race between devfsd and minilogd (remeber syslogd hasn't yet
> be started since it's a service launched after rc.sysinit let rc play
> with init levels.
>
> we've found a solution: make a service of the previous piece of script
> and run it very late (ie in 99th position whereas syslogd service has
> a priority of 88).
Ug! I hate work-arounds. Can you put time into helping track down
whether there is a bug in devfs or devfsd, and what the cause of the
bug is?
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|