Prevent CrashPlan service from starting automatically on reboot

[InterClaw]

When you reboot the NAS, CrashPlan is set to start its service, right? It will do so even if I manually stopped it with "./CrashPlanEngine stop" before rebooting, correct?

How do I prevent it from starting automatically on reboot? I don't want to uninstall it.

[StephenB · Accepted solution]

If disable isn't available, then I'd either try chmod or break the symlink.  You should be able to create a new symlink later on.

[StephenB]

I think update-rc.d crashplan disable should work, using update-rc.d crashplan enable to reverse.

Alternatively you could try chmod -x /etc/init.d/crashplan, using chmod +x /etc/init.d/crashplan to reverse.

[InterClaw]

Running your first suggestion, I got this result: 

usage: update-rc.d [-n] [-f] <basename> remove
update-rc.d [-n] <basename> defaults [NN | sNN kNN]
update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
-n: not really
-f: force

 So I tried this: 

update-rc.d crashplan remove

... and then it said this: 

update-rc.d: /etc/init.d/crashplan exists during rc.d purge (use -f to force)

 Not sure if I should do this. What do you think Stephen? Maybe something should be changed in /etc/init.d/crashplan instead? It looks like this:

#!/bin/sh
# Linux Standard Base comments
### BEGIN INIT INFO
# Provides:          CrashPlanEngine
# Required-Start:    $local_fs $network $remote_fs
# Required-Stop:     $local_fs $network $remote_fs
# Should-Start:
# Should-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: CrashPlan Engine
# Description:       CrashPlan backup service engine
### END INIT INFO

#############################################################
# Init script for CrashPlanEngine
#############################################################

# Defaults
SCRIPTNAME=/usr/local/crashplan/bin/CrashPlanEngine

case "$1" in
start)
        $SCRIPTNAME start
        ;;
stop)
        $SCRIPTNAME stop
        ;;
restart)
        $SCRIPTNAME restart
        ;;
force-reload)
        $SCRIPTNAME force-reload
        ;;
status)
        $SCRIPTNAME status
        ;;
*)
        echo "Usage: $0 <start|stop|restart|force-reload|status>" >&2
        exit 3
        ;;
esac
exit 0

[InterClaw]

Okay, now I'm learning things about runlevels... Seems like default runlevel for the NAS is 2? in /etc/rc2.d there's S01readynas_startup and S99crashplan. This is the only runlevel where crashplan is it seems.

Also seems like this update-rc.d disable is a new feature that might not be available in this semi-old Linux environment?

So removing is more permanent. Why is the force flag needed? Seems like S99crashplan is just a symlink to /etc/init.d/crashplan, which is the real startup script? So if I delete it from rc.d and want to restore it, can I just manually recreate the symlink in /etc/rc2.d, call it S99crashplan, pointing at /etc/init.d/crashplan, and it will work? Or is there more to it? 

[StephenB · Accepted solution]

If disable isn't available, then I'd either try chmod or break the symlink.  You should be able to create a new symlink later on.

[InterClaw]

Perfect. I used the chmod approach, so the system doesn't have access to run that script on boot (I'm guessing is what I did ).

I verified with ./CrashPlanEngine status after a reboot and the service stayed off.

[mdgm-ntgr]

It's better where possible to use systemd service files rather rc.d scripts.

With systemd you have greater control over when the service starts, which services must start first etc.

[InterClaw]

Either you completely missed the point of the topic, or this is some weak phishing attempt.

[mdgm-ntgr]

Thanks for reporting this. peterstrong was a spammer and his posts have been removed.