In a default configure (simply "./configure" without any config options
set) and build of clamav, what temporary directory does clamav use by
default - that is, the temporary directory that can be overridden with
the following clamscan flag?:
--tempdir=DIRECTORY Create temporary files in DIRECTORY
Also, is there a way to determine (say long after clamav has been
installed and the original build directory deleted) what user and group
clamav may have been configured to use during "./configure"?:
--with-user=uid name of the clamav user (default=clamav)
--with-group=gid name of the clamav group (default=clamav)
What seems to be happening is if someone has built clamav to use some
other uid/gid than "clamav", then the unofficial-sigs.sh download script
can fail with "ERROR: Can't write to temporary directory", for example:
======================================================================
SaneSecurity phish.ndb Signature File Update
======================================================================
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 191k 100 191k 0 0 66204 0 0:00:02 0:00:02 --:--:-- 128k
ERROR: Can't write to temporary directory
This happens at the point in the script where clamscan is attempting to
verifying that the signature file is valid (not corrupted), for example:
clamscan -v -d /var/tmp/clamdb/phish.ndb - < /dev/null
And again, it only seems to be happening when clamav is built to use
some other uid/gid than the default of "clamav". If someone that is
experiencing this "ERROR: Can't write to temporary directory" creates a
temporary directory and sets the uid/gid permissions to match the
uid/gid that clamav was configured to use during build, and then uses
the "--tempdir=" flag with clamscan pointing to this newly created
temporary directory, then the script runs to completion without error.
Thus my original questions, where is the default temporary director used
by clamscan, and how does one determine what uid/gid clamav was possibly
configured to use after-the-fact? Also, does anyone have any other
suggestions on possible ways to overcome this issue by some other means?
TIA for any feedback...
Bill
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
