Currently, crond's service file has: [Unit] Description=Command Scheduler After=syslog.target network.target sssd.service ypbind.service Arguably, cron should run after remote-fs.target as well, as user jobs may rely on the remote filesystem. This affects all later versions of Fedora too.
You are right. In previous releases with the sysvinit script was crond started at the last service. Sadly, I can't do that in unit.
Hm, could you try change the unit file? [Unit] Description=Command Scheduler After=syslog.target network.target sssd.service Before=systemd-user-session.service I'll fix it in all releases at once as soon as I do a little testing. I might even remove sssd.service from the unit.
Marcela, Note the correct spelling is the plural form: systemd-user-sessions.service You may have been confused by my typo in bug 809132. Also note that I suggested to have cron start After systemd-user-sessions.service, not Before.
(In reply to comment #3) > Marcela, > Note the correct spelling is the plural form: systemd-user-sessions.service > You may have been confused by my typo in bug 809132. > > Also note that I suggested to have cron start After > systemd-user-sessions.service, not Before. Oops. So it should be: [Unit] Description=Command Scheduler After=syslog.target network.target sssd.service systemd-user-sessions.service
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I fixed it in F-18+