On Fri, 2004-03-26 at 18:53, Costas Magkos wrote: [...] > Is there a way to test whether a chroot works? Does anyone know if the > above syslog option is really needed? According to the man page of > syslog it is needed.
use lsof # lsof -p [pid number of bind process] check: - if the loaded libraries is in the chroot (by cheking the path and/or the inode) - if std in/out and err are connected inside the chroot to /dev/null - there is only one socket to syslog (in the real world) -- JJ van Gorkum Knowledge Zone If UNIX isn't the solution, you've got the wrong problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
