There appears to be a race condition in the new sshd bootscript. The first time I ran sshd it complained of /proc//oom_adj not existing. The second time it said /proc/<previous PID>/oom_adj doesn't exist. Perhaps a slight sleep after starting sshd to ensure the pid file is created/updated before. Or maybe use pidof or something. I'll test it out in a few.
-- Archaic Want control, education, and security from your operating system? Hardened Linux From Scratch http://www.linuxfromscratch.org/hlfs -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
