From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Can not run sshguard as a service
Date: Sun, 02 Feb 2020 20:52:10 +0100 [thread overview]
Message-ID: <20200202195210.jxUeYqfaBdq4Hebg0Jf1YzjUudDeED2IMAcOBZayOnI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17728@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
Closed issue by kotoko on void-packages repository
https://github.com/void-linux/void-packages/issues/17728
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 5.3.18_1 X86_64 GenuineIntel uptodate rFFF`
* packages:
* `sshguard-2.4.0_1`
* `openssh-8.1p1_1`
* `socklog-2.1.0_5`
### Expected behavior
You can start sshguard service using `sv` command.
### Actual behavior
`sv` command times out and kills process.
### Steps to reproduce the behavior
Assuming you have already running ssh server. I am using socklog as logger.
```
$ xbps-install sshguard
$ ln -s /etc/sv/sshguard-socklog /var/service
$ sv up sshguard-socklog
timeout: down: sshguard-socklog: 1s, normally up, want up
```
### Comment
So it looks like sshguard is running as normal program without forking/going to background by itself. It is running as long as executable is executing. On the other hand `sv` expects that all commands end within few seconds or it fails. I did experiment and run as root `sshguard` and tested with failed login attempt to ssh server. It worked as expected (banned me). So it is just problem with running.
Second thing I noticed is that there is passed `-l` (small L) as parameter which is no longer supported. I think there is mandatory file `/etc/sshguard.conf` for configuration.
next prev parent reply other threads:[~2020-02-02 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17728@inbox.vuxu.org>
2020-01-02 17:42 ` voidlinux-github
2020-01-02 17:43 ` voidlinux-github
2020-01-02 17:46 ` voidlinux-github
2020-02-02 19:52 ` voidlinux-github [this message]
2020-02-02 19:56 ` voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200202195210.jxUeYqfaBdq4Hebg0Jf1YzjUudDeED2IMAcOBZayOnI@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).