Matt, I told you about this before, but completely forgot about it. After doing considerable testing on my test servers, i thought -current was safe enough to try on our production shell servers. I installed -current on one of my servers, and to my dismay, it hung. :)
Within 5 minutes of running, nearly every process is blocked on 'inode', with the exception of a single 'cp' stuck in vmopar. I have a very silly, *very* poorly written script i run out of cron, every 10 mins or so, to update my passwd and group files. #/bin/sh cp /home/private/passwd /etc cp /home/private/master.passwd /etc cp /home/private/group /etc rm /etc/spwd.db.tmp >/dev/null 2>&1 pwd_mkdb /etc/master.passwd This script is the only source of a 'cp' anywhere... If I turn this off, I was able to run for at least 30 mins(more, if i hadn't rebooted) /home is a UDP NFS2 mount. Moving the source of those cp's to a local drive also fixes the problem, but breaks the use for my script. :) What more info do you need for help in debugging this? Kevin To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
