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!
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!
FS#43442 - [mailman] gate_news timer broken
Attached to Project:
Community Packages
Opened by David Runge (dvzrv) - Wednesday, 14 January 2015, 17:02 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 17 February 2015, 00:53 GMT
Opened by David Runge (dvzrv) - Wednesday, 14 January 2015, 17:02 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 17 February 2015, 00:53 GMT
|
DetailsDescription:
The included timer for the gate_news (NNTP polling and sending to lists) functionality is not correct: On activation: systemctl start mailman-gatenews.timer "[/usr/lib/systemd/system/mailman-gatenews.timer:5] Failed to parse calendar specification, ignoring: */5:00:00" If it's a daily thing (at 5AM), it should be 05:00:00 instead! If it should be every 5 minutes, one could just set: OnUnitActiveSec=5m instead of using OnCalendar. Additional info: mailman 2.1.18.1-2 Steps to reproduce: - Install mailman - systemctl start mailman-gatenews.timer |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Tuesday, 17 February 2015, 00:53 GMT
Reason for closing: Fixed
Additional comments about closing: mailman-2.1.18.1-3
Tuesday, 17 February 2015, 00:53 GMT
Reason for closing: Fixed
Additional comments about closing: mailman-2.1.18.1-3
Comment by Dave Reisner (falconindy) -
Wednesday, 14 January 2015, 17:44 GMT
Shouldn't OnUnitActiveSec be OnUnitInactiveSec? If you use the former, something would need to kickstart the feedback loop. Using the latter should mean that the unit runs ~5 minutes after bootup, and ~5 after each run finishes.