I am using CrashPlan Linux to back up to the cloud. It has a system service that is supposed to start at boot. I have a script installed in /etc/init.d which is properly linked to /etc/init.d/S99crashplan. On boot, the service is not started, nor does crashplan show up as a service in the Yast Services Manager application. I open a root command line and enter systemctl enable crashplan and systemctl start crashplan and the service starts. It also shows up in the Yast Services Manager as both active and enabled with LSB: CrashPlan Engine in the Description field. On the next boot, however, the service doesn’t start nor does in show up in the Services Manager until I manually enter the systemctl commands.
The CrashPlan support site is no help as it has instructions for OpenSuse 12.3 which suggest to enter sudo insserv /etc/init.d/crashplan on a command line. I understand this is obsolete. Nonetheless, I’ve tried it and it does start CrashPlan, but again, it does not automatically start on the next reboot.
How can I get this program to start automatically on boot?
The CrashPlan support site is no help as it has instructions for OpenSuse 12.3 which suggest to enter sudo insserv /etc/init.d/crashplan on a command line. I understand this is obsolete.
Even if it is obsolete, it still works as long as your software continues to ship legacy initscript instead of systemd unit.
If you run insserv as suggested it should create correct link(s) for you. If you want to do it manually, links should go into /etc/init.d/rcN.d for run-level N.
I ran insserv as you suggested and it did create the proper links – thanks. Unfortunately, crashplan still did not start. I did manage to get it to start on boot by adding a direct reference to the crashplan script in /etc/init.d/after.local – the command /etc/init.d/crashplan start.
Do I still need the links that insserv created in rc5.d? Does it matter if they are there or not?
On Thu, 21 Apr 2016 18:56:01 +0000, bearymore wrote:
> I ran insserv as you suggested and it did create the proper links –
> thanks. Unfortunately, crashplan still did not start. I did manage to
> get it to start on boot by adding a direct reference to the crashplan
> script in /etc/init.d/after.local – the command /etc/init.d/crashplan
> start.
>
> Do I still need the links that insserv created in rc5.d? Does it matter
> if they are there or not?
>
> Thanks for your help.
I would take a look at the log and see why it’s failing to start.
One reason could be missing dependencies. Your description sounds like it needs network, and it may be started before network. Quite a lot of program would fail in this case. As suggested you need to check logs to find out why it fails to start the first time.