Hi David,
Do we need to fix your problems before we fix my problem?
By the way, I've been poking around to see how other init scripts deal with the fact that /var/run is flushed after every reboot.
This is how /etc/init.d/klogd makes sure that it has a subdirectory in /var/run:
case "$1" in start) log_begin_msg "Starting kernel log daemon..." # create klog-writeable pid and fifo directory mkdir -p /var/run/klogd chown klog:klog /var/run/klogd mkfifo -m 700 $kmsgpipe chown klog:klog $kmsgpipe
And this is how /etc/init.d/slony1 does it:
prepare_start() { mkdir -p /var/run/slony1 \ && chown postgres:postgres /var/run/slony1/ \ && chmod 2775 /var/run/slony1/ }
So, it does not look like a standard method exists. I would like to get some really good sysadmins to help us with this. There really should be a standard way to do this.
Matt
Hi David,
Do we need to fix your problems before we fix my problem?
By the way, I've been poking around to see how other init scripts deal with the fact that /var/run is flushed after every reboot.
This is how /etc/init.d/klogd makes sure that it has a subdirectory in /var/run:
case "$1" in
start)
log_begin_msg "Starting kernel log daemon..."
# create klog-writeable pid and fifo directory
mkdir -p /var/run/klogd
chown klog:klog /var/run/klogd
mkfifo -m 700 $kmsgpipe
chown klog:klog $kmsgpipe
And this is how /etc/init.d/slony1 does it:
prepare_start() {
mkdir -p /var/run/slony1 \
&& chown postgres:postgres /var/run/slony1/ \
&& chmod 2775 /var/run/slony1/
}
So, it does not look like a standard method exists. I would like to get some really good sysadmins to help us with this. There really should be a standard way to do this.
Matt