[Savannah-hackers-public] mgt insserv sysync loop issues

[Bob Proulx]

I started installing (re-installing) munin on mgt.  I didn't expect
any problems.  But this displayed various init.d script errors
relating to sysync.  (Somewhat abreviated.  I removed some of the
repetition.)

  insserv: warning: script 'K20sysync' missing LSB tags and overrides
  insserv: warning: script 'sysync' missing LSB tags and overrides

The above is the root of the problem that cascades down through these
others below.

  insserv: There is a loop at service sysync if started
  insserv: There is a loop between service munin-node and checkroot if started
  insserv:  loop involving service checkroot at depth 3
  insserv:  loop involving service mountdevsubfs at depth 2
  insserv: There is a loop at service munin-node if started
  insserv: There is a loop between service munin-node and mountnfs if started
  insserv:  loop involving service mountnfs at depth 2
  insserv:  loop involving service networking at depth 1
  insserv:  loop involving service mountnfs-bootclean at depth 4
  insserv:  loop involving service screen-cleanup at depth 6
  insserv: There is a loop between service sysync and mountall-bootclean if 
started
  insserv:  loop involving service mountall-bootclean at depth 2
  insserv:  loop involving service mountall at depth 1
  insserv: Starting sysync depends on munin-node and therefore on system 
facility `$all' which can not be true!
  insserv: Starting sysync depends on munin-node and therefore on system 
facility `$all' which can not be true!
  insserv: Starting sysync depends on munin-node and therefore on system 
facility `$all' which can not be true!
  ...
  insserv: Starting sysync depends on munin-node and therefore on system 
facility `$all' which can not be true!
  insserv:  loop involving service mountoverflowtmp at depth 8
  insserv:  loop involving service checkfs at depth 5
  insserv: There is a loop between service sysync and ifupdown-clean if started
  insserv:  loop involving service ifupdown-clean at depth 1
  insserv: Starting sysync depends on munin-node and therefore on system 
facility `$all' which can not be true!
  insserv: Starting sysync depends on munin-node and therefore on system 
facility `$all' which can not be true!
  insserv: Starting sysync depends on munin-node and therefore on system 
facility `$all' which can not be true!
  insserv:  loop involving service hwclockfirst at depth 4
  insserv:  loop involving service hostname at depth 5
  insserv: There is a loop between service munin-node and mountall if started
  insserv:  loop involving service mtab at depth 7
  insserv: There is a loop between service munin-node and mountoverflowtmp if 
started
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing munin-node (--configure):
   subprocess installed post-installation script returned error exit status 1
  configured to not write apport reports
                                        Errors were encountered while 
processing:
   munin-node
  E: Sub-process /usr/bin/dpkg returned an error code (1)

I would like to learn more about sysync so that I could fill in the
Description and Short-Description appropriately but in the meantime I
am going to add the following LSB header to address this problem.

  ### BEGIN INIT INFO
  # Provides:          sysync
  # Required-Start:    $remote_fs $syslog
  # Required-Stop:     $remote_fs $syslog
  # Default-Start:     2 3 4 5
  # Default-Stop:
  # Short-Description: Sysync user/group sync tool
  # Description:       Sysync is a tool to manage users/groups and
  #                    configuration files across multiple hosts.
  ### END INIT INFO

That makes insserv happy when ordering the boot time rc symlinks.

I rather silently did not install any stop symlinks because I don't
think this service needs to be stopped at reboot.  There has been a
general move to avoid spending cpu cycles to stop processes that don't
need an explicit shutdown sequence to be happy and thinking this is in
that category I didn't stop it.

And with the above package installation is happy again.  Yay!

Bob