Re: [SSHGuard-users] openrc incorrect status

[Kevin Z. <kev...@gm...>]

Thanks for the report. I think there's a suggestion on how to completely
kill things off, but we need to test more to make sure things work
consistently across all operating systems.

I think eventually we'll have to rewrite the driver script in C to get
some sort of consistency... I was hoping we wouldn't have to do that but
shells seem to do different things across the board.

On 4/7/19 3:51 PM, giant@cock.email wrote:
> This is in reply to the mail thread last written to on 2019-02-14.
> 
> I also stumbled across this issue. OpenRC can track sshguard better if
> you use the --pidfile flag in start-stop-daemon, as such
> 
>   start-stop-daemon --start --wait ${SSHGUARD_WAIT} --background --quiet
> --pidfile ${SSHGUARD_PIDFILE} --exec \
>    /usr/sbin/sshguard -- -i ${SSHGUARD_PIDFILE} ${SSHGUARD_OPTS}
> 
> However, referring to below excerpt from the sshguard shell-script
> (/usr/sbin/sshguard on Alpine Linux), when the service is stopped,
> sshg-blocker and the shell-script will be killed, but the $tailcmd and
> sshg-parser will continue, orphaned.
> 
> eval $tailcmd | $libexec/sshg-parser | \
>     $libexec/sshg-blocker $flags | ($BACKEND; kill -PIPE $$)
> 
> I don't know why that is.
> 
> 
> _______________________________________________
> sshguard-users mailing list
> ssh...@li...
> https://lists.sourceforge.net/lists/listinfo/sshguard-users


-- 
Kevin Zheng
kev...@gm... | ke...@be... | PGP: 0xC22E1090