First boot-up today, and the problem persists without any change, so apparently network unavailability is not a factor in my case (the connection is always made very early after the desktop appears). Somehow a delay on boot would have to be programmed into the Freshclam scheduler in order to solve this problem.
Paul > Thanks to everyone who responded. For some reason I cannot Reply to mails from this list. I have to Compose from scratch each time, which probably breaks threading here. Here is my original response, resending now: > Thanks very much, Micah! I have ethernet here and it does connect quickly, but this still might be happening. I'm made the emendation and will let you know if it solves the problem or not. It will take a few days to be sure. I still think that a delay mechanism is very desirable, perhaps even as the default. BW, Paul On Mon, Aug 12, 2019 at 9:24 AM Micah Snyder (micasnyd) <micasnyd at cisco.com> wrote: >> >> This may be related, another user had noted that freshclam was starting >> before it had network access, and had us add a network-online dependency to >> the service file. This change will be present in the 0.102 release, but you >> can always add it manually to your clamav-freshclam.service file: >> https://bugzilla.clamav.net/show_bug.cgi?id=12104 >> >> -Micah _______________________________________________ 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
