Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31063 - [systemd] Cannot disable (or even locate) crond.service in systemd 187-4

Attached to Project: Arch Linux
Opened by John (graysky) - Wednesday, 08 August 2012, 15:36 GMT
Last edited by Tom Gundersen (tomegun) - Thursday, 09 August 2012, 21:31 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Since this update, I noticed systemd wants to load crond.service. I use cronie.serivce which loads just fine. No idea how crond.service get into the enabled list, nor how to disable -- or even find -- the service file. Is this a bug or PEBKAC?

$ systemctl | grep fail
crond.service loaded failed failed Legacy unit for crond

I have no idea how to disable crond.service which doesn't seem to exist on my filesystem.

$ locate service | grep cron
/etc/systemd/system/multi-user.target.wants/cronie.service
/usr/lib/systemd/system/cronie.service

# systemctl disable crond.service
Failed to issue method call: No such file or directory

Additional info:
* package version(s) 187-4


Steps to reproduce:
Boot a system running systemd and inspect the output of `systemctl`
This task depends upon

Closed by  Tom Gundersen (tomegun)
Thursday, 09 August 2012, 21:31 GMT
Reason for closing:  Fixed
Comment by Dave Reisner (falconindy) - Wednesday, 08 August 2012, 15:47 GMT
I don't know what "this update" is, but it's probably because you have initscripts-systemd installed.
Comment by John (graysky) - Wednesday, 08 August 2012, 15:49 GMT
@Dave - "This update" meaning the 187-4 release. Should have made that more clear. I do not have that package installed.

$ pacman -Ss systemd
core/libsystemd 187-4 [installed]
systemd client libraries
core/systemd 187-4 [installed]
system and service manager
core/systemd-sysvcompat 187-4
sysvinit compat for systemd
core/systemd-tools 187-4 [installed]
standalone tools from systemd
community/initscripts-systemd 20120704.1-1
Arch specific systemd initialization/bootup scripts for systemd
community/systemd-arch-units 20120704-1 [installed]
Arch specific Systemd unit files
Comment by Dave Reisner (falconindy) - Wednesday, 08 August 2012, 15:53 GMT
Ah, this is part of initscripts now. crond is being pulled in because DAEMONS is parsed out of rc.conf
Comment by John (graysky) - Wednesday, 08 August 2012, 16:24 GMT
Ah! That makes sense:

$ grep DAE /etc/rc.conf
DAEMONS=(syslog-ng ufw network @netfs @crond @dbus @ntpd @cpupower @sensors @gpm @samba @psd @fancontrol @cupsd)

Should I open a bug against initscripts? This should not be the expected behavior.
Comment by Dave Reisner (falconindy) - Wednesday, 08 August 2012, 16:52 GMT
No, this is already fixed in SVN.
Comment by Tom Gundersen (tomegun) - Thursday, 09 August 2012, 10:37 GMT
This is fixed in cronie in [testing].

For the future, if you are experienceing problems please first try

# systemctl status crond.service

It should have told you where the mysterious unit file comes from :)
Comment by John (graysky) - Thursday, 09 August 2012, 20:50 GMT
Nice, I can confirm that the package in [testing] fixes this problem. Plz close this buggy.

Loading...