On Wed, 28 Jan 2015, Wilfred van Velzen wrote to mark lewis:

 WvV>> but I don't find it more difficult to turn on or off services. 
 WvV>> What's difficult about 'systemctl start|stop ' ?

 ml> you've misunderstood... that's after they've been turned on/off... 
 ml> until they've been turned on, they can't be automatically executed 
 ml> by the system at specific times...

 WvV> You mean 'sysctl enable ' ?

i guess so unless that's part of systemd... much of what we do is handled
manually, though... we can easily take an existing script and modify it
slightly for our item and off we go...

 WvV> After you have done that you can call 'systemctl start|stop
 WvV> ' commands from any cron job.

we've never done that and don't intend to do so... /etc/init.d/foo start/stop
is more our style and it is built into our muscle thought memory banks ;)

 ml> we have execution scripts in /etc/init.d and we softlink them into 
 ml> the various /etc/rc*.d directories... each has its own starting 
 ml> ''rank'' putting it in the proper order needed during sysinit... 
 ml> there's also links to them for shutting them down at specific 
 ml> times... the sysv stuff knows whether to call the scripts with 
 ml> "start" or "stop" based on the link name...

 WvV> You're describing regular sysv functionality here, so...?

yes, and that's what we're going to continue to use without systemd sticking
its ugly face into everything ;) 

)\/(ark