Bug 670116

It is possible though to start crond manually:

$ service crond status
crond.service - Command Scheduler
	  Loaded: loaded (/lib/systemd/system/crond.service)
	  Active: active (running) since Sat, 15 Jan 2011 18:12:18 +0100; 2s ago
	Main PID: 26656 (crond)
	  CGroup: name=systemd:/system/crond.service
		  └ 26656 /usr/sbin/crond -n

I added into post new line, just to be sure crond will be added:
/bin/systemctl enable crond.service >/dev/null 2>&1 || :

But I'm also seeing Active: inactive (dead). I suppose cron daemon should be running after installation, especially when I have jobs to be executed.

(In reply to comment #2)
> But I'm also seeing Active: inactive (dead). I suppose cron daemon should be
> running after installation, especially when I have jobs to be executed.

No, it should not. "Installations can be in changeroots, in an installer context, or in other situations where you don't want the services started."

(In reply to comment #3)
Since 'chkconfig --list crond' does return
  crond  0:off  1:off  2:on  3:on  4:on  5:on  6:off
which was the default setting, systemd should actually bring up cron: if not it is a bug.

On reboot, yes. Directly after package installation... no.

Hmm, my guess is that the spec file of the cronie package is missing the right %triggerun directives to make sure that when upgrading from a cronie package that only has sysv scripts to one that ships both sysv scripts and systemd unit files cronie is enabled in systemd if and only if the sysv service was previously enabled. 

See https://fedoraproject.org/wiki/TomCallaway/Systemd_Revised_Draft#Unit_files_in_spec_file_scriptlets for details, specifically the part about "To facilitate upgrades from older packages carrying SysV scripts, add the following scriptlet:".

Does the cronie package contain such a directive?

(In reply to comment #6)
> Hmm, my guess is that the spec file of the cronie package is missing the right
> %triggerun directives to make sure that when upgrading from a cronie package
> that only has sysv scripts to one that ships both sysv scripts and systemd unit
> files cronie is enabled in systemd if and only if the sysv service was
> previously enabled. 
> 
> See
> https://fedoraproject.org/wiki/TomCallaway/Systemd_Revised_Draft#Unit_files_in_spec_file_scriptlets
> for details, specifically the part about "To facilitate upgrades from older
> packages carrying SysV scripts, add the following scriptlet:".
> 
> Does the cronie package contain such a directive?

I'd like to remind you that's only a draft. You should really start cooperating with FPC people sooner and rawhide would be working better at the moment.

Are you saying that all daemons will need this ugly hack to be safely updated? Usually we are trying to avoid triggers at all because errors in them is hard to fix and make specfiles unreadable. I'll wait with fix until final decision of FPC.

(In reply to comment #7)
> (In reply to comment #6)
> > Hmm, my guess is that the spec file of the cronie package is missing the right
> > %triggerun directives to make sure that when upgrading from a cronie package
> > that only has sysv scripts to one that ships both sysv scripts and systemd unit
> > files cronie is enabled in systemd if and only if the sysv service was
> > previously enabled. 
> > 
> > See
> > https://fedoraproject.org/wiki/TomCallaway/Systemd_Revised_Draft#Unit_files_in_spec_file_scriptlets
> > for details, specifically the part about "To facilitate upgrades from older
> > packages carrying SysV scripts, add the following scriptlet:".
> > 
> > Does the cronie package contain such a directive?
> 
> I'd like to remind you that's only a draft. You should really start cooperating
> with FPC people sooner and rawhide would be working better at the moment.

I have been talking to Spot all the time. I am not sure what gets you to the conclusion I wasnt cooperating with them.

> Are you saying that all daemons will need this ugly hack to be safely updated?

Yes.

> Usually we are trying to avoid triggers at all because errors in them is hard
> to fix and make specfiles unreadable. I'll wait with fix until final decision
> of FPC.

Well, that part has already been agreed on (not officially though).

Anyway, reassigning to cronie, since this should be fixed in the cronie .spec file.

It wasn't fixed yet.

(In reply to comment #10)
For me, the issue was resolved some time ago. It never occurred again after installing TC2 from scratch. And finally, what is this?

* Mon Jan 17 2011 Marcela Mašláňová <mmaslano redhat com> - 1.4.6-8
- enable crond even with systemctl

But there is still missing daemon-reload line, which could be crucial in some cases. I'm still waiting for approval of packaging draft.

cronie-1.4.7-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/cronie-1.4.7-2.fc15

Package cronie-1.4.7-2.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cronie-1.4.7-2.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/cronie-1.4.7-2.fc15
then log in and leave karma (feedback).

cronie-1.4.7-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.