innd bootup script is crippled. creating PID file in non existent dir.

Bug #164767 reported by puccha
2
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%3a1.7.2debian-31_i386", affected lines are 9,10,11,12 where /var/run/news should be replaced by /var/run/innd.

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-daemon --quiet --start --exec /etc/news/boot
    ;;
  stop)
    echo -n "Stopping news server:"
    if [ -f /var/run/innd/innwatch.pid ]; then
      echo -n " innwatch"
      start-stop-daemon --quiet --stop --oknodo \
        --pidfile /var/run/innd/innwatch.pid
    fi

Revision history for this message
puccha (yuri-schaeffer) wrote :

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.

Daniel T Chen (crimsun)
Changed in inn:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.