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#31913 - [bacula] pid files created in wrong place by both rc.d and systemd startup
Attached to Project:
Community Packages
Opened by Mark (fiddlinmacx) - Friday, 12 October 2012, 14:22 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 26 October 2012, 03:18 GMT
Opened by Mark (fiddlinmacx) - Friday, 12 October 2012, 14:22 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 26 October 2012, 03:18 GMT
|
DetailsDescription: Both rc.d and systemd startup create pid files in /var/run even though bacula is compiled to do so in /var/run/bacula. For rc.d this causes 'rc.d stop bacula-*' to fail and for systemd this causes 'systemctl start bacula-*' to fail because it can't find the runfile. It's looking in /var/run/bacula but the file's in /var/run
The error looks like this: PID file /var/run/bacula/bacula-fd.9102.pid not readable (yet?) What is going on? Additional info: * latest version as well as previous ones |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Friday, 26 October 2012, 03:18 GMT
Reason for closing: Won't fix
Friday, 26 October 2012, 03:18 GMT
Reason for closing: Won't fix
Comment by Sven-Hendrik Haase (Svenstaro) -
Friday, 26 October 2012, 03:17 GMT
Bacula has been dropped to aur.