[clamav-users] clamscan (NOT clamdscan) log file setup in *.conf file?

[G.W. Haywood]

Hi there,

On Fri, 18 Nov 2016, Noel Jones wrote:

> Perhaps it would be useful for clamscan to read (some?) options from
> a config file, or even better from environment variables. Feel free
> to open a bug report/feature request and make your case.

This would be what I'd call 'feature creep'.

Any competent sysadmin can code a script to get clamscan to do
whatever it's capable of doing, both with much more flexibility and
with many fewer gotchas than any config file (plus parser).  If the
sysadmin isn't competent then getting clamscan to jump through hoops
is hardly the greatest of his problems.

Think of utilities like 'find' and 'xargs' for example.  These are
fully-fledged, heavily used and well-tested tools.  The ClamAV team
has better things to be doing with its time than re-inventing wheels
of that kind.

-- 

73,
Ged.