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#32518 - [monit] Systemd Unit File
Attached to Project:
Community Packages
Opened by Paul Gideon Dann (giddie) - Wednesday, 07 November 2012, 12:41 GMT
Last edited by Balló György (City-busz) - Wednesday, 11 September 2013, 17:56 GMT
Opened by Paul Gideon Dann (giddie) - Wednesday, 07 November 2012, 12:41 GMT
Last edited by Balló György (City-busz) - Wednesday, 11 September 2013, 17:56 GMT
|
DetailsA couple of issues with the unit file:
1) Monit will not be restarted if it crashes. Can you add Restart=always to the unit? 2) Because the unit is set to start after network.target, it's possible that some services that Monit is intended to monitor have not started when Monit is started. Can this be changed to default.target, so that Monit is only started after the default target is reached? (Is this a sensible way of dealing with this?) Additional info: * monit 5.5-2 |
This task depends upon
Closed by Balló György (City-busz)
Wednesday, 11 September 2013, 17:56 GMT
Reason for closing: Won't implement
Additional comments about closing: ask upstream
Wednesday, 11 September 2013, 17:56 GMT
Reason for closing: Won't implement
Additional comments about closing: ask upstream
But anyway, you can customize the unit files on your system as described here:
https://wiki.archlinux.org/index.php/Systemd#Editing_provided_unit_files