Another clue?
When I run 'samba stop', nmbd fails. The process has stopped, and the PID remains. When I then run 'samba start', it fails with nmbd as there is already a PID. Running 'samba stop' a second time it reports that the process ID given to nmbd isn't running, and must remove the PID file because I can then run 'samba start' succesfully. So I guess I could try to stop the hang at shutdown(caused by the script message that I shouldn't be seeing this error) by attempting to kill nmbd twice. But I would really like to work out what the problem is in the first place. But I guess the next step is to put the harddrive with LFS on it(currently in my computer) into the box I plan on using as a server to see if everything is working before worrying about it to much. My concern is that it will be harder to shutdown/reboot and correct this problem with only SSH for access in the 'server' box.
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
