WD MyCloud and Minimserver

[Tbanks103]

(07-02-2018 19:56)simoncn Wrote:  Thanks for confirming this. The only other difference is the S99 change. This appears to default to S01 if NN is not specified as an argument to update-rc.d, which would cause MinimServer to be started earlier in the boot process than with S99. Some descriptions of update-rc.d don't mention the NN argument, so I am not sure whether I can rely on this working for all platforms. If you could try "out of the box" (which I presume would use S01), I would appreciate it.

I am not familiar with either .legacy-bootordering or insserv. MinimServer doesn't use either of these.

To try and unravel the update-rc.d knot a little, I tried the following:

MyBookLive:~# update-rc.d -n minimserver defaults
Adding system startup for /etc/init.d/minimserver ...
/etc/rc0.d/K20minimserver -> ../init.d/minimserver
/etc/rc1.d/K20minimserver -> ../init.d/minimserver
/etc/rc6.d/K20minimserver -> ../init.d/minimserver
/etc/rc2.d/S20minimserver -> ../init.d/minimserver
/etc/rc3.d/S20minimserver -> ../init.d/minimserver
/etc/rc4.d/S20minimserver -> ../init.d/minimserver
/etc/rc5.d/S20minimserver -> ../init.d/minimserver

The default priority of 20 is obviously arbitrary, and anyway not appropriate for the corresponding shutdown stages (the K's - which should be at 100-the S's priority), but this result describes which rcN.d links are created. Note that the -n option is for 'don't actually do anything'

Instead, I tweaked the command and tested out the following:

MyBookLive:~# update-rc.d minimserver start 85 2 3 4 5 . stop 15 0 1 6 .
Adding system startup for /etc/init.d/minimserver ...
/etc/rc0.d/K15minimserver -> ../init.d/minimserver
/etc/rc1.d/K15minimserver -> ../init.d/minimserver
/etc/rc6.d/K15minimserver -> ../init.d/minimserver
/etc/rc2.d/S85minimserver -> ../init.d/minimserver
/etc/rc3.d/S85minimserver -> ../init.d/minimserver
/etc/rc4.d/S85minimserver -> ../init.d/minimserver
/etc/rc5.d/S85minimserver -> ../init.d/minimserver

Priority 85 is what is used by another (ahem) media server on my installation.

This can't be a global (all unixes) solution, since - as described here - BSD distributions don't have the rcN.d directories, and some other Linux's have them, but not the update-rc.d command. Could you test for the presence of the command?