Package: runit-services
Version: 0.2.3
Severity: normal
Tags: patch
Many people are now mounting /var/run (and /var/lock) as tmpfs
directories. This is done on debian systems by adding the following
lines to /etc/default/tmpfs:
RAMRUN=yes
RAMLOCK=yes
This is useful for read-only root filesystems, among other
circumstances.
However, this means that initscripts (or their variants) need to take
responsibility for building out any directories they need in those
directories.
running sshd under runit on a system with these tmpfs's fails, logging
this message:
2007-04-28_16:55:29.42128 Missing privilege separation directory: /var/run/sshd
The patch below fixes things for me.
Thanks for maintaining runit in debian! It's the cleanest initscript
system out there, IMHO.
--dkg
--- /etc/sv/ssh/run.orig 2007-04-28 13:04:24.000000000 -0400
+++ /etc/sv/ssh/run 2007-04-28 12:55:28.000000000 -0400
@@ -4,6 +4,9 @@
# sshd wants to be started with absolute pathname
SSHD=$(which sshd) || sv down $(pwd)
+PRIVSEP_DIR=/var/run/sshd
+mkdir -p "$PRIVSEP_DIR"
+
exec "$SSHD" -D -e
# memory limits set by chpst are inherited to subprocesses,
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
