I recentlyposted a summary on this topic which suggested tidy methods for locking
the passwd file while it is being edited.
Th lock file suggested was
<path of passwd text file>.ptmp
for a NIS environment.
We tried this under SunOS 4.1.1, and found that although the lock file appeared to be the correct one, locking it had a severe effect on yppasswdd, either causing it to
crash or hang.
viz:
Oct 29 15:16:09 sysa yppasswdd[29956]: password file busy - try again.
Oct 29 15:16:09 sysa yppasswdd[29956]: yppasswdd: couldnt reply to RPC call
Oct 29 15:16:09 sysa yppasswdd[29956]: svc_run: - select failed: Bad file number
Oct 29 15:16:09 sysa yppasswdd[29956]: yppasswdd: svc_run shouldn't have returned
We contacted Sun about this, and were told this was a known bug in yppasswdd, and it
would be fixed when "NIS+" was released. I saw a description of this in the SUG (UK)
proceedings, and wonder when is it likely to appear?
G.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:17 CDT