[artix-general] [s6] clamd + freshclam configs and internet connectivity

[Javier]

On 9/21/21 07:32, Dudemanguy wrote:
> I've got some good news. I've actually been working on implementing
> primitive network detection in s6-scripts. If you've noticed, there's a
> network oneshot in your /etc/s6/sv directory right now. It's not very
> good though, so I have not made use of it. I'm working on a way to make
> this better and to allow users to leverage it and use it as a dependency
> for any service they run. My goal is to get it land in core this week.

Ohh, that's pretty good news, though there are several official services/oneshots that would benefit from it, so not sure if only the users should take advantage of it.  Freshclam is just an example, but there are others, like ntpd, smbd and nmbd.  Not sure, but I suspect dnsmasq would also benefit from it, and there might be others, like services provided over internet, like email and such...  So perhaps on your final commit, you make those official services/oneshots requiring internet connection depend on the "network" one.  BTW, some time back, for personal purposes I tried making some oneshot of mine depending on "network", but it was failing, given the interfaces were not up when trying to bring the oneshot up.  But I'd guess it was too early to test the dependency, hehe...  As of now, "network" only checks for the ethernet interfaces to be up, but that doesn't mean there's internet connection available yet, not sure if that's part of your changes, hehe...  I just stop depending on it, since it didn't mean what I really needed any ways, hehe

> By all means, feel free to disable any service-specific logging options
> like that. I personally much prefer using s6-log for logging, so
> eliminating redundancy is a good thing. As long as the daemon writes its
> logging output to stdout and/or stderr, s6-log will catch it. For things
> that log to syslog, I recommend installing and enabling syslogd-s6.
> There are other syslog daemons out there of course, but syslogd uses
> pure s6 tooling to read /dev/log and it integrates perfectly with
> s6-log. If you are using an s6 setup, it is far superior to syslog-ng,
> and others imo.

Not sure if all daemons configs provide such "system" logging configs.  I'm sure mpd does.  I don't know if by commenting out logs destinations make daemons log into sddout/stderr, actually I'm not sure if choosing "system" logs for mpd, makes mpd log into stdout/stderr, but I'll install syslog-ng and syslog-ng-s6.  When I installed artix with s6, I though it was not necessary given s6 came with its own logger, hehe.

Thanks a lot !

-- 
Javier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.artixlinux.org/archives/artix-general/attachments/20210921/0f6ce047/attachment-0001.sig>