<html><head></head><body><div>I use it to quell my paranoid mode to scan my debian laptop</div><div><br></div><div>On Thu, 2023-01-19 at 08:09 +0100, Stefan Hornburg (Racke) wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On 18/01/2023 21:59, Sébastien Villemot wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On Tue, 29 Jun 2021 22:08:31 +0200 Sebastian Andrzej Siewior <<a href="mailto:sebastian@breakpoint.cc">sebastian@breakpoint.cc</a>> wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On 2020-05-30 19:53:49 [+0000], Patrick Schleizer wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>package clamav-daemon ships a file /usr/bin/clamonacc which is a<br></div><div>background virus scaning guard / real-time protection. It's currently<br></div><div>non-trivial to use.<br></div><div><br></div><div>sudo clamonacc<br></div><div><br></div><div>ERROR: Clamonacc: at least one of OnAccessExcludeUID,<br></div><div>OnAccessExcludeUname, or OnAccessExcludeRootUID must be specified ... it<br></div><div>is reccomended you exclude the clamd instance UID or uname to prevent<br></div><div>infinite event scanning loops<br></div><div><br></div><div>May I suggest adding an init script / systemd unit file which runs the<br></div><div>clamonacc background scanner?<br></div></blockquote><div><br></div><div>The config file has to be touched manually to configure it properly. In<br></div><div>the past this was part of clamd and people managed to lockup / deadlock<br></div><div>their systems. Therefore I hesitate to add an initscript here.<br></div><div>However I agree that even with proper configuration an initscript would<br></div><div>be nice here since there is no need to over complicate it.<br></div><div><br></div><div>Feel free to post something (by someone who is actually using it),<br></div><div>otherwise I try to add something later on.<br></div></blockquote><div><br></div><div>As of clamav-daemon 1.0.0+dfsg-5, a systemd unit is provided for<br></div><div>clamonacc, so it looks like this issue has been addressed.<br></div><div><br></div><div>However, the unit is enabled by default. This looks like a bug, because<br></div><div>the service fails to start with the default configuration.<br></div><div><br></div></blockquote><div><br></div><div>IMHO it doesn't make sense to be enabled as default even if it would start properly.<br></div><div>Most common use of ClamAV is to scan emails.<br></div><div><br></div><div>Regards<br></div><div> Racke<br></div><div><br></div></blockquote><div><br></div><div><span></span></div></body></html>