NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
InterClaw
May 19, 2016Aspirant
Prevent CrashPlan service from starting automatically on reboot
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 fro...
- May 19, 2016
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
May 19, 2016Guru - Experienced User
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.
- InterClawMay 19, 2016Aspirant
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
- InterClawMay 19, 2016Aspirant
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? :smileytongue:
- StephenBMay 19, 2016Guru - Experienced User
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.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!