The foreground option prevents clamd from forking and running in the background.
For users who run it from the terminal it means that it stays in the foreground
and the user will continue to see output from clamd on the terminal, will need
a new terminal to run anything else, and closing the term
Just wanted to wave to Gary, another Solaris 11.3 user.
There aren't many of us left.
Regards, Scott
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Help us build a comprehensiv
+1
Thanks,
Pierre
On 12 Apr 2018 at 13:39, SCOTT PACKARD wrote:
Just wanted to wave to Gary, another Solaris 11.3 user.
There aren't many of us left.
Regards, Scott
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/c
I am out of the office Thursday, April 12 and Friday April 13. I will be
returning Monday, April 16.
If you need immediate assistance, please contact Amy Harding
. Her extension is 126.
--
David Conner
Metropolitan Reporting Bureau
Phone (800) 245-6686 X101
Fax (800) 343-9047
___
On 11.04.18 10:24, paul.gu...@gmail.com wrote:
On my Raspbian system htop reports clamd runs with the -foreground=true
option, although I have commented that out in the configs.
your raspbian apparently uses systemd, process manager who prefers to run
applications in foreground (because in case
Background: Using ClamAV for Win32. My usage has allowed me to use
it without ever having to install it. Instead I simply extracted the
.msi. Updates were done by replacing previous files with new ones.
The directory structure of the extracted .msi from the
clamav-0.100.0-win-x86.zip file i
