https://bugzilla.redhat.com/show_bug.cgi?id=2350109 --- Comment #50 from Pramod V U <pramodvu1502@xxxxxxxxx> --- > Yes, absolutely. Vixie-Cron or Cronie will either watch these location with some os-provided facility (iselect()...) or poll these every minute. > > Also, when systemd-cron's "crontab" modify files in /var/spool...; > it does not communicate with the generator and can not anyway. > > The current `systemctl daemon-reload` is the only way to refreh correclty & only once. Agreed > Fedora has "crontabs" that fill a similar purpose. > https://packages.fedoraproject.org/pkgs/crontabs/crontabs/ But we have to supply the group and tmpfiles.d snippet for `/var/spool/cron`. I think it would be better if those too would be in this shared package... Anyways, adding the systemd-userdb JSON records in my fork... > In practice if packages in Fedora Depends: on "cronie" and nothing else that makes systemd-cron uninstable. Do the other cron daemons like fcron do `Provides: cronie`? If yes, then we too must do it... > That's not how it works. Upstream should not be bothered after each 50 attemps to nudge a specfile in the right direction. I'm considering removing this contrib/ file altogether as soon as this package is accepted. I agree, but the copr needs the specfile to be with the sources... in the same repository... OR a custom script (which I used until now, heredoc-ing the spec-file into it); But now the character limit is reached. I'll just use the custom script but with `git` pulling the specfile separately (from *my* github repo maybe). OR does someone have a better solution? > There's no /etc/cron.boot in Fedora; please stay in line with what "cronie" & "crontabs" do. Fine; I am disabling support for the boot timer... > I've no idea how to untangle this knot. Maybe just use `Provides: cronie` for now... > Maybe in the same way as "/usr/sbin/sendmail", using "alternatives"? Great idea... But what? `crontabs` binary... > This will require changes in cronie... Just temporarily resort to `Provides: cronie`... Once everything else sorted out we'll see into this... -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2350109 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202350109%23c50 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
