innd bootup script is crippled. creating PID file in non existent dir.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
inn (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: inn
When installing inn, the daemon starts and works properly. Upon rebooting the machine innd doesn't get started cleaming it can not descent into the directory /var/run/innd.
Some investigation learned that the script /etc/init.d/inn contained some inconsistencies about which directory should contain the pid file. Below is a portion of the script as directly extracted from "inn_1%
Since this prefends inn to start both automaticly and manually after a reboot I suggest a critical status. Luckely with a dead-easy fix.
##### /etc/init.d/inn #########
#!/bin/sh -e
#
# Start/stop the news server.
test -f /usr/sbin/innd || exit 0
case "$1" in
start)
if [ ! -d /var/run/news ]; then ## CONFLICTING LINE
mkdir -p /var/run/news ## CONFLICTING LINE
chown news:news /var/run/news ## CONFLICTING LINE
chmod 775 /var/run/news ## CONFLICTING LINE
fi
start-
;;
stop)
echo -n "Stopping news server:"
if [ -f /var/run/
echo -n " innwatch"
start-
--pidfile /var/run/
fi
Changed in inn: | |
status: | New → Fix Released |
attached the complete standard init script. Extracted directly from "inn_1% 3a1.7.2debian- 31_i386. deb" downloaded via aptitude using ubuntu server 7.10.