I have tried using the tcpsocket parameter on the clamd.conf. I have tow
different clamd instances running on different servers. While I can get the
clamdscan to talk to the local (on the same server) clamd instance, I cannot
get clamdscan to talk to an remote instance of clamd running on a di
Hi there,
On Wed, 3 Apr 2019, Kretschmer, Jens wrote:
I would like to redirect the output of clamscan to the journal ...
man logger
Do you have any idea what could be causing the issue?
It's not clear to me which system you're using, but try
man cron
--
73,
Ged.
__
Also, it should be totally unnecessary to scan your filesystem every
minute, and will place an unnecessary load on your server. Postfix (or
whatever) will run clamav when it needs to. And you can maybe run a full
scan on your filesystem once every 24 hours if you feel paranoid.
(IMHO.)
Postfix
You can configure a log specially for clamav, and that should be plenty.
Also, you can install logwatch and get mail updates once a day or more
often. You can also install netdata if you want to monitor in real time,
or simply watch the output of 'tail -f /var/log/clamav/clamav.log'
it's e
Logfiles are a place where a sysadmin notices a host running smoothly (lack of
anything in logs) or has problems (error messages about the programs show up in
the logs).
Looks like you are trying to misuse logfiles as a place to put
successful/unsuccessful output that's produced by a program.
Yo
Hi,
I would like to redirect the output of clamscan to the journal, which should by
possible by
/usr/bin/clamscan -r /root/ 2>&1 | /usr/bin/systemd-cat --identifier="clamscan"
or
/usr/bin/systemd-cat --identifier="clamscan" /usr/bin/clamscan -r /root/
While both commands work when executed manuall
