the problem with the default start order for the services still exists
with:
autofs 4.1.4-11
nis 3.17-2
from browsing the thread i understand that this issue requires some
coordination between the nis and autofs packages and that the current
thought is that it should be fixed in nis.
it would be great if this could be sorted out before etch is released.
while there are workarounds, it would be a shame to go into the next
release with a broken-by-default configuration for a (not uncommon)
environment using nis and autofs.
thanks!
andy
--
"man! today is so loopy!" - the tick
