FS#33050 - systemd ignores commented out rc.conf DAEMON variable
Attached to Project:
Arch Linux
Opened by Ernestas (ernetas) - Tuesday, 11 December 2012, 20:05 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 12 December 2012, 23:45 GMT
Opened by Ernestas (ernetas) - Tuesday, 11 December 2012, 20:05 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 12 December 2012, 23:45 GMT
|
Details
Description: systemd ignores commented out rc.conf DAEMON
variable
I had such lines in rc.conf: #DAEMONS=(crond NetworkManager) DAEMONS=() But the crond script still reported that rc.d is in use: ernestas ~ $ sudo systemctl status crond crond.service - LEGACY unit for "crond" rc script Loaded: loaded (/etc/rc.conf) Active: failed (Result: exit-code) since Tue, 2012-12-11 22:03:04 EET; 31s ago Docs: man:arch-daemons(8) Process: 13936 ExecStart=/etc/rc.d/crond start (code=exited, status=1/FAILURE) Process: 13932 ExecStartPre=/usr/bin/echo WARNING: A legacy rc script is being used. Consider removing this from your DAEMONS array and enabling a native systemd service instead. (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/crond.service Dec 11 22:03:04 pluto systemd[1]: Starting LEGACY unit for "crond" rc script... Dec 11 22:03:04 pluto echo[13932]: WARNING: A legacy rc script is being use...d. Dec 11 22:03:04 pluto crond[13936]: [106B blob data] Dec 11 22:03:04 pluto systemd[1]: Failed to start LEGACY unit for "crond" r...t. Dec 11 22:03:04 pluto systemd[1]: Unit crond.service entered failed state Warning: Unit file changed on disk, 'systemctl --system daemon-reload' recommended. ernestas ~ $ sudo systemctl start crond |
This task depends upon
Closed by Dave Reisner (falconindy)
Wednesday, 12 December 2012, 23:45 GMT
Reason for closing: Not a bug
Wednesday, 12 December 2012, 23:45 GMT
Reason for closing: Not a bug
The simple solution would just be to uninstall initscripts.
P. S. I rebooted a few dozens of times after commenting out rc.conf DAEMONS as I was using a only systemd services for 3 months now.