We found the problem ourselves. truss'ing automountd revealed that it
was crashing when reading /etc/netmasks. Due to past history, our yp
netmask was 143.xxx 255.255.255.192 and had never given us any
problems. By changing /etc/netmasks on both SS1000's to
188.8.131.52 255.255.255.192 (i.e. the inclusion of zeroes to complete
the network number), both systems' automountd started to behave
This is strange, given that the global yp mask is still
143.106 255.255.255.192 and that ypbind is invoked (/etc/rc2.d/S71...)
before automountd (/etc/rc2.d/S73...). Also, other 2.3 machines never
exhibited such behaviour with the same setup.
So, we're correcting the global yp netmask map as well (we'll add
zeroes to the network number)...
I forgot to mention that /etc/nsswitch.conf had the correct entry for
the above reasoning:
netmasks: nis [NOTFOUND=return] files
Also, the machine is also running NSkit (nis server), though it
exhibited the same behaviour without it.
-- postmaster/manager Paulo Licio de Geus INTERNET: email@example.com Depto de Ciencia da Computacao voice: +55 192 39-3115/8695/8442 DCC - IMECC - UNICAMP fax: +55 192 39-7470/5808 caixa postal: 6065 13081-970 Campinas SP Brazil
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:13 CDT