On Mon, Dec 19, 2005 at 08:39:10AM -0800, Dennis Peterson wrote:
>
> In fact it would be nice to have a command line switch that generates a
> listing of what is seen and understood by the applications after reading
> the clamd.conf and freshclam.conf files, as well as where they were found.
<delurk>
Postfix's postconf(1) is an excellent model for this:
postconf [no args]: print the entire running config
postconf <var-name>: print just that variable. -h to omit the 'name=' part.
postconf -d: print the default values of known config variables
postconf -n: print only non-default or explicitly set variables
postconf -e: edit a config variable
There are other options to list supported map types and locking methods
that wouldn't be as relevant to a theoretical clamconf(1). It's
scripting-friendly, and gives a standard set of installation info to post
to the ML for help
There are plenty of apps I have to deal with that I wish had an equivalent
of postconf.
cheers
rob
</delurk>
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
(text/plain)