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#53229 - sshguard 2.0.0-1 does not start
Attached to Project:
Community Packages
Opened by Tim (sirarch) - Thursday, 09 March 2017, 20:17 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 09 March 2017, 23:50 GMT
Opened by Tim (sirarch) - Thursday, 09 March 2017, 20:17 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 09 March 2017, 23:50 GMT
|
DetailsDescription:
sshguard just got upgraded to 2.0.0-1 and it no longer starts: sshguard: Could not read '/usr/etc/sshguard.conf' sshguard: Please configure SSHGuard. Not sure why it's looking for /usr/etc/sshguard.conf, that looks like the wrong location, maybe it was compiled with the wrong options? Additional info: * package version(s): 2.0.0-1 * config and/or log files etc. sshguard: Could not read '/usr/etc/sshguard.conf' sshguard: Please configure SSHGuard. Steps to reproduce: systemctl start sshguard wait a bit systemctl status sshguard |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 09 March 2017, 23:50 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#53228
Thursday, 09 March 2017, 23:50 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Jan de Groot (JGC) -
Thursday, 09 March 2017, 20:27 GMT
Probably needs --sysconfdir=/etc in configure.
Comment by Tim (sirarch) -
Thursday, 09 March 2017, 20:34 GMT
Looks like a dup. Please close.