> That's interesting.  Are you getting a "could not lock the passwd  
> file: EOPNOTSUPP" failure with rpc.lockd not enabled? 

Negative, I rebuild the kernel on one box today, commented out 
rpc.lockd="YES" in /etc/rc.conf and rebooted into single user mode and 
remounted / rw.

I then ran adduser:

[some output deleted]
Home       : /home/koekoek
Shell      : /bin/sh
Locked     : no
OK? (yes/no): pw: group update: Operation not supported
pwd_mkdb: flock: Operation not supported
pw: user 'koekoek' disappeared during update
adduser: ERROR: There was an error adding user (koekoek).

and uploaded the kdump to 
http://members.iphouse.com/robertj/ktrace.adduser.no.rpc.lockd.txt, same 
story with vipw:

vipw: could not lock the passwd file: : Operation not supported


After that, I rebooted once again into the normal 
multi-user modus with rpc.lockd running and took ktraces for vipw and 
adduser (http://members.iphouse.com/robertj/ktrace.vipw.rpc.lockd.txt 
and http://members.iphouse.com/robertj/ktrace.adduser.rpc.lockd.txt 
respectively) for the record.

The pxe box runs 5.4-RELEASE-p11, being served by a 4.11-RELEASE-p19 box.

Please feel free to contact me to let me do something else, test or 


PS: koekoek is a bird, dutch for Cuculus Canorus :-)
freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to