The way that we figure what services we don’t need is by stopping them one by one until the cloud no longer responds and then we reboot and continue stopping the other services until we figure the minimal number services that the machine will need to work and vice versa like when we find that we can no longer connect to the drive, we start up the services one by one until such service like SMB starts to work again.
Of course there is the other more intellectual method such as Google but we tend to fall asleep on the technical terms such as “procps” which is the package that has a bunch of small useful utilities that give information about processes using the /proc filesystem. When we wake up we go back to simply shutting them down one by one until the machine doesn’t work.
I really think it is funny that the WD forums are community based rather than the Tech guys from WD answering our questions. It is the blind leading the blind, or perhaps some of us are more near sighted or far-sighted than blind but nevertheless none of us know for sure why the customers of a product are trying to solve a problem other than WD saving money on tech support.
So I thought maybe we should start up a thread that discovers what a service does, document it and then we can sticky it at the top of this User Community Forum.
So all the following files has the following command structure
/etc/init.d/monitorio stop <=== to stop the services
/etc/init.d/monitorio status <=== to inquire whether the services is running or stopped
/etc/init.d/monitorio restart <=== restart by performing a stop and start
/etc/init.d/monitorio start <=== starts up the service.
monitorio links to the monitorio script in
/usr/local/sbin/monitorio.sh of which you can edit and modify than restart the script using the above command.
This is the same for samba which is the SMB that Rac was talking about…
Here we go, lets list out all the services that we can stop and find out what they do… or google it and come up with a nice succinct description of the service. However I want none of that circular descriptive that says something like
ramlog handles all the ram logs and stops all the rams from logging.
The first thing I did was to go to the /etc/init.d directory and do a “ls -a1” and here are all the /etc/init.d scripts that can be started, re-started and stopped, and if you were like me, you would say…
hey there is a README at the top of the list…
WDMyCloud:/etc/init.d# cat README
Configuration of System V init under Debian GNU/Linux
Most Unix versions have a file here that describes how the scripts
in this directory work, and how the links in the /etc/rc?.d/ directories
influence system startup/shutdown.
For Debian, this information is contained in the policy manual, chapter
“System run levels and init.d scripts”. The Debian Policy Manual is
The Debian Policy Manual is also available in the Debian package
“debian-policy”. When this package is installed, the policy manual can be
found in directory /usr/share/doc/debian-policy. If you have a browser
installed you can probably read it at
Some more detailed information can also be found in the files in the
Debian Policy dictates that /etc/init.d/*.sh scripts must work properly
when sourced. The following additional rules apply:
* /etc/init.d/*.sh scripts must not rely for their correct functioning
on their being sourced rather than executed. That is, they must work
properly when executed too. They must include “#!/bin/sh” at the top.
This is useful when running scripts in parallel.
* /etc/init.d/*.sh scripts must conform to the rules for sh scripts as
spelled out in the Debian policy section entitled “Scripts” (§10.4).
Use the update-rc.d command to create symbolic links in the /etc/rc?.d
as appropriate. See that man page for more details.
All init.d scripts are expected to have a LSB style header documenting
dependencies and default runlevel settings. The header look like this
(not all fields are required):
BEGIN INIT INFO
Required-Start: $remote_fs $syslog
Required-Stop: $remote_fs $syslog
Default-Start: 2 3 4 5
Default-Stop: 0 1 6
Short-Description: Example initscript
Description: This file should be used to construct scripts to be
# placed in /etc/init.d.
END INIT INFO
More information on the format is available from insserv(8). This
information is used to dynamicaly assign sequence numbers to the
boot scripts and to run the scripts in parallel during the boot.
See also /usr/share/doc/insserv/README.Debian.
So lets begin defining them. I’ll leave it empty for now and as user’s contribute their definition of what that services does or perhaps the consequences, such as the device rebooted or died after I stopped the service: warning don’t do that…