From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: sshguard: support dynamic firewall config and remove iptables dependency
Date: Thu, 23 Jan 2020 15:31:49 +0100 [thread overview]
Message-ID: <20200123143149.zJmZ1J7---qdMKSl31t5LyXEW69qJwkdzLFzXcRWxjs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18477@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/18477#issuecomment-577706121
Comment:
> Maybe a symlink like `/etc/sv/sshguard-socklog -> /etc/sv/sshhuard/` would work but that would need to be tested, I can't remember a prior case of renaming a service.
I thought about a symlink but thought it was too problematic. There is some precedent: xbps-alternatives creates a symlink from /etc/sv/crond to the chosen alternative service. In this case, however, I think there is a high probability of a collision when users create an sshguard service to avoid the iptables dependency.
> Another solution might be an `INSTALL` script that changes the symlink in `/var/service` if it exists already, but that seems a bit hacky. Its an interesting issue and finding a clean solution might help in the future.
If the INSTALL script finds an existing link, and the target of that link is also a link to the new service name, the user could be prompted with a yes/no question about migrating the link. This will alert all affected users to the change and provide a one-key option to resolve the issue. Maybe some helper functions common/ could encapsulate a procedure like this for all packages.
prev parent reply other threads:[~2020-01-23 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 21:41 [PR PATCH] " voidlinux-github
2020-01-22 21:49 ` voidlinux-github
2020-01-23 0:54 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-23 1:03 ` voidlinux-github
2020-01-23 10:53 ` [PR PATCH] [Merged]: " voidlinux-github
2020-01-23 10:53 ` voidlinux-github
2020-01-23 14:31 ` voidlinux-github [this message]
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=20200123143149.zJmZ1J7---qdMKSl31t5LyXEW69qJwkdzLFzXcRWxjs@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).