[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#366893: init.d stopping messages not standardized or even always logged

Package: general
Severity: wishlist

Looking at the myriad ways of starting messages in /var/log/boot,
Starting X TrueType font server: xfstt.
Starting /usr/sbin/chronyd...
Starting anac(h)ronistic cron: anacron.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler....
(especially that last mystery program one), got me looking at
start/stop messages.  Stop messages for example:

We see poor convergence of start messages in /etc/init.d:
$ cd /etc/init.d/
$ grep -i stopping *
acpid:  echo -n "Stopping Advanced Configuration and Power Interface daemon: "
apache2:		log_begin_msg "Stopping apache 2.0 web server..."
atd:	log_daemon_msg "Stopping deferred execution scheduler" "atd"
bind:	echo -n "Stopping domain name service: named"
bootlogd:	log_daemon_msg "Stopping $DESC" "$NAME"
cpufreqd:		log_daemon_msg "Stopping $DESC" "$NAME"
cron:stop)	log_begin_msg "Stopping periodic command scheduler..."
cupsys:	echo -n "Stopping $DESC: $NAME"
cwdaemon:    echo -n "Stopping $DESC: $NAME"
dbus-1:  echo -n "Stopping $DESC: "

Also even
$ grep --files-without-match -i stopping [a-z]*|wc -l

Despite policy:
          When you stop or restart a daemon, you should issue a message
          identical to the startup message, except that `Starting' is
          replaced with `Stopping' or `Restarting' respectively.

However, even policy's
$ zgrep -i stopping policy.txt.gz
  echo -n "Stopping domain name service: named"
isn't as systematic as
  echo -n "Stopping $DESC: $NAME"
Therefore, policy should provide a better role model.

However, I also notice that although there is a bootlogger to log all
those starting messages, upon shutdown syslog or whatever is shutdown
too early in the order of shutting things down, so that many of those
"stopping" messages, or errors upon stopping, aren't logged at all!

Reply to: