Hi there, On Sat, 10 Oct 2020, Robert Kudyba wrote:
... next time it happens I can try some of these: ...
But put some logging in place before it does, so you get as precise a timeline as you can.
Here's what the -i option returns: ... Loading config: /etc/clamav-unofficial-sigs/master.conf Loading config: /etc/clamav-unofficial-sigs/os.conf Loading config: /etc/clamav-unofficial-sigs/user.conf
I take it you've examined these files for clues? And the systemd unit files etc.?
... the convenience of starting on reboot ...
People used to do that before systemd. :) You can e.g. just put a command line in /etc/rc.local to get the same effect. The trouble with systemd is it breaks such a lot of things. The final straw for me was when it killed an fsck at boot time because it thought it had been running for too long (90 seconds) leaving me with a trashed 3TB drive and quite a bit of work to put it back together. One of the many claims people make about it is dependable naming of the Ethernet interfaces. Unfortunately they're dependably named something else, so your remote systems suddenly go dark and you have to get in the Jeep. Oh, sorry, wrong list.
... professor ... Xmas eve ... emails are held back ...
You can probably set it up so that mail flows if ClamAV isn't running, although most people would probably say that's not a great idea.
Frippery! Ha another one you made me look up. ... Thanks ...
Just returning some favours. It's how it all works. :) -- 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
