My Cloud slept for 3 days 5 hours after killing OpenVPN

Hi there Kazgor,

There is a whole thread on sleep somewhere around here ( click here) including remounting the drive which seems to go hand in hand with killing all the scans.

but for OpenVPN you will need to ssh into the device 

use 

ps -ALL 

to see all the process that are running.  if you see openVPN running then you can 

use

killall openvpn

you can also stop the service by

/etc/init.d/openvpn stop

or restart the service by

/etc/init.d/openvpn start

However remember that openvpn is part of the remote and without it, I think your cloud services won’t work; at least that is what I remember back in the days when I was killing all the services in order to find sleep.

So as I said, this is only one of many services that wakes up the cloud. 

/etc/init.d/nfs-kernel-server stop

/etc/init.d/nfs-common stop

/etc/init.d/upnp_nas stop

/etc/init.d/mDNSResponder stop

/etc/init.d/wdphotodbmergerd stop

/etc/init.d/wdnotifierd stop

/etc/init.d/wdmcserverd stop

/etc/init.d/wddispatcherd stop

Final ingrediants to Sleep (credits goes to Rac8006, so give him the kudos for being persistent)

  1. adding an extra sync to the monitorio script helps a lot with reducing the number of 7 second wake ups down to only one or two per night.

  2. after SSH’ing into the device issue the following mount command… don’t worry nothing untoward will happen and if it does, blame Rac8006 please…

mount -o remount,noatime,nodiratime /dev/root /

you could also use mine

mount -o remount,noatime /dev/root /

The difference is that I assume noatime encompassing nodiratime.