lux-integ wrote: > On Wednesday 31 July 2013 12:13:42 Armin K. wrote: >> You don't need systemd service for hwclock. Systemd has timedated, a >> daemon which handles the clock. man timedatectl > > thanks > > I duly did man man timedatectl and found hwclock married up with ntp et al > one needing a user passwd to access!. > http://www.freedesktop.org/software/systemd/man/timedatectl.html > ehmm .. > Why is control taken away from the sysadmin to start/stop programs such as > hwclock ntpd, to mount/unmount filesystems etc?
Because systemd knows better than you do. For example if I have an ipv6 > setup with ntpd; this has slightly different calling options from > one with ipv4 , same for dhcpd, dhclient etc etc. Yet this seems > inconsequential in systemD; indeed I recall dhclient was not even supported. > . And unit files do not support conditional processing, it is a start/stop > affair and thats it. The more I delve into it, the more I am finding systemd > a straightjacket-onsize-fits-all monstrosity. Well, yes. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
