Jan Christoph Nordholz wrote: > Hi Luk, Hi
>>>> It seems that autofs is started before nfs-common which apparently >>>> prevents automounting of nfs partitions. Changing the symlink from >>>> S19autofs to S21autofs to make sure it gets started after S20nfs-common >>>> seems to fix the problem. >>> shuffling the autofs link around would open Pandora's box again - see >>> #400952. We're talking about a similar corner case here, as nfs-common >>> is also in rcS.d/44... so the admin must have switched to single-user and >>> back to get hit by the bug (or /usr/sbin was not available at rcS.d/44). > >> Not true as rcS.d/44 < 19 < 20 > > Excuse me? That's the point I was trying to make... unless something has > prevented nfs-common from firing up its daemons that early, nfs-common > should have been started before autofs during normal bootup, obscuring the > bug: > > ] /etc/rcS.d/S44nfs-common > ] /etc/rc2.d/S19autofs > ] /etc/rc2.d/S20nfs-common > > leaving only two scenarios: > > a) rcS.d/S44nfs-common didn't start anything (e.g. no /usr yet) > b) a runlevel chain S->[2345]->1-*>[2345] (bug surfaces at the last > transition) > > the latter being in complete analogy to portmap (rcS.d/S43, rc[2345].d/S17) in > #400952. It appears to be a). Any hints on how to figure out why nfs-common is not starting anything? Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
