Rudder

Rudder provides a very nice init script: rudder-server-root. This script starts all required components for the Rudder server.
However, Ubuntu (unlike RHEL/CentOS) defaults to create startup links for every package it installs. So, by default all required
components for the Rudder server are started twice at boot (at least they're trying to do so).

AFAIK there's two sulotions to solve this:

• remove the rudder-server-root startup links and leave the others
• Remove the indivual startup links and only leave the rudder-server-root startup link

The rudder-server-root script already can do all the work, so personally I'd prefer to remove the other startup links. I found
this out because after rebooting jetty didn't come up correctly. I did the following so solve it, rebooted the Rudder server, and
all services came up fine.

root@rudder-server-root:~# update-rc.d -f slapd remove
 Removing any system startup links for /etc/init.d/slapd ...
root@rudder-server-root:~# update-rc.d -f postgresql remove
 Removing any system startup links for /etc/init.d/postgresql ...
   /etc/rc0.d/K21postgresql
   /etc/rc1.d/K21postgresql
   /etc/rc2.d/S19postgresql
   /etc/rc3.d/S19postgresql
   /etc/rc4.d/S19postgresql
   /etc/rc5.d/S19postgresql
   /etc/rc6.d/K21postgresql
root@rudder-server-root:~# update-rc.d -f rudder-agent remove
 Removing any system startup links for /etc/init.d/rudder-agent ...
   /etc/rc0.d/K20rudder-agent
   /etc/rc1.d/K20rudder-agent
   /etc/rc2.d/S20rudder-agent
   /etc/rc3.d/S20rudder-agent
   /etc/rc4.d/S20rudder-agent
   /etc/rc5.d/S20rudder-agent
   /etc/rc6.d/K20rudder-agent
root@rudder-server-root:~# update-rc.d -f rudder-jetty remove
 Removing any system startup links for /etc/init.d/rudder-jetty ...
   /etc/rc0.d/K20rudder-jetty
   /etc/rc1.d/K20rudder-jetty
   /etc/rc2.d/S20rudder-jetty
   /etc/rc3.d/S20rudder-jetty
   /etc/rc4.d/S20rudder-jetty
   /etc/rc5.d/S20rudder-jetty
   /etc/rc6.d/K20rudder-jetty