Ged,
That's a fair assessment. This is why I asked.
Thanks,
Micah
On 9/13/19, 11:26 AM, "clamav-users on behalf of G.W. Haywood via
clamav-users" <clamav-users-boun...@lists.clamav.net on behalf of
clamav-users@lists.clamav.net> wrote:
Hi there,
On Fri, 13 Sep 2019, Micah Snyder (micasnyd) via clamav-users wrote:
> One thing we could do is have clamd "start" before loading the
> database. That is to say that it would immediately begin listening
> on the unix/tcp socket for requests and fork into the background so
> as not to block the boot process. All scan requests would then be
> blocked while the database loads. I imagine this would solve most
> of the frustration around boot-up load time.
I don't think you should be trying to second-guess stuff like this,
and I don't quite see how in these days of parallel boot processes
that anything will get blocked that doesn't need to be blocked. Will
you be looking at the network interfaces? The routes? You'll end up
writing another systemd. The system administrator/integrator needs to
earn his living somehow; not asking a utility to do things when it's
not yet ready to do them is one of his jobs. It's why there are all
those symlinks in /etc/rc3.d/.
> Does this have any appeal?
Seems like a waste of effort to me.
--
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
_______________________________________________
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
