Differences between version 2 and previous revision of ChrootNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Tuesday, March 11, 2008 3:33:40 pm | by JohnMcPherson | Revert |
| Older page: | version 1 | Last edited on Tuesday, March 11, 2008 3:14:42 pm | by JohnMcPherson | Revert |
@@ -1,9 +1,19 @@
-!
!!Syslog inside your chroot
+!!Syslog inside your chroot
I had a few issues getting syslog to work -
# In debian, the start-stop-daemon program used to start syslog finds the existing syslog running (ie the one outside the chroot) and won't start another one. I fixed this by changing a line in <tt>/etc/init.d/sysklogd</tt> from "<tt>start-stop-daemon --start --quiet --exec $binpath -- $SYSLOGD</tt>" to simply "<tt>$binpath $SYSLOGD</tt>"
# make sure you have all the device files it needs - eg /dev/log and /dev/console
# syslog wouldn't open any output log files until I copied <tt>/etc/services</tt> and restarted it - otherwise it doesn't know what port it should listen on...
+!!SSH
+There is a patchset for ssh to allow you to chroot specific users. If you just use a normal chroot and normal ssh instead,
+and you get errors like
+<pre>sshd~[1234]: error: openpty: No such file or directory
+</pre>
+or
+<pre>
+error: session_pty_req: session 0 alloc failed
+</pre>
+then you are missing /dev/ptmx. Try "<tt>mknod /dev/ptmx c 5 2</tt>".
--
Also see chroot(8)
