Re: [clamav-users] what initiates freshclam? [OT]

2022-01-07 Thread Kenneth Porter
--On Friday, January 07, 2022 10:45 AM -0500 Kris Deugau 
 wrote:



IIRC most of that one can be laid at the feet of the kernel developers
trying to make hardware enumeration more predictable, and systemd is just
one of several places the sysadmin can try to clean up the pieces.


Agreed. I recommend taking further discussion of systemd to its own list:

https://lists.freedesktop.org/archives/systemd-devel

(Unless it's discussion of how ClamAV interacts with systemd, such as in 
the optional unit files for launching freshclam that can replace the old 
crontab drop-in file.)



___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml


Re: [clamav-users] what initiates freshclam? [OT]

2022-01-07 Thread Kris Deugau

G.W. Haywood via clamav-users wrote:

IMHO this is a pretty unconvincing reason to change your init system,
especially to one which is both as new as systemd, and as capable of
stupidity on a scale never before seen in any init system.  A couple
of examples here (the wanton renaming of Ethernet interfaces


IIRC most of that one can be laid at the feet of the kernel developers 
trying to make hardware enumeration more predictable, and systemd is 
just one of several places the sysadmin can try to clean up the pieces.


My understanding is about 50% "WTF?", but supposedly the change came 
about because a physical device on a known physical slot location will 
show up in the PCI hardware enumeration in a semirandom order.  The 
people having most issue with this were people using "many" multiport 
NICs to build routers, and they were apparently having real problems 
with logical interfaces semirandomly migrating from card to card to 
card.  When you're actively trying to decide where to fling packets 
around this is a Big Problem(TM).


-kgd

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml


Re: [clamav-users] what initiates freshclam? [OT]

2022-01-07 Thread G.W. Haywood via clamav-users

Hi there,

On Fri, 7 Jan 2022, Kenneth Porter wrote:


...
One reason to switch to systemd is that you no longer need to implement a 
random delay in your own script to reduce server load from lots of client 
scripts slamming the server at the top of the hour. See the 
RandomizedDelaySec and FixedRandomDelay options in the timer help.


There's a metaphor about babies and bathwater around here somewhere.

IMHO this is a pretty unconvincing reason to change your init system,
especially to one which is both as new as systemd, and as capable of
stupidity on a scale never before seen in any init system.  A couple
of examples here (the wanton renaming of Ethernet interfaces and, to
the amazement of all concerned, the killing of an ext3 fsck boot job
because it took longer then 90 seconds) both necessitated trips to
remote sites to recover from the installation of systemd by Debian's
packaging system during the upgrade to 'Buster'.

Be very sure you've tested the new setup if you switch to systemd.

Personally, I avoid it like covid-19.

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml