ports/60135: clamav startup failure: unable to create directory in /var/tmp
Peter N.M.Hansteen
peter at datadok.no
Thu Dec 11 11:00:40 UTC 2003
>Number: 60135
>Category: ports
>Synopsis: clamav startup failure: unable to create directory in /var/tmp
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Dec 11 03:00:37 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Peter N. M. Hansteen
>Release: FreeBSD 5.1-RELEASE-p10 i386
>Organization:
>Environment:
System: FreeBSD rosalita.datadok.no 5.1-RELEASE-p10 FreeBSD 5.1-RELEASE-p10 #2: Thu Oct 16 06:18:12 CEST 2003 root at rosalita.datadok.no:/usr/obj/usr/src/sys/GENERIC i386
>Description:
On a fresh install of clamav, running the port's startup script fails
with what looks like a failure to create a temporary directory in /var/tmp:
rosalita# /usr/local/etc/rc.d/clamav-clamd.sh start
Starting clamav_clamd.
LibClamAV Error: cli_cvdload(): Can't create temporary directory /var/tmp//2f337bc40e520172
ERROR: Unable to create temporary directory.
>How-To-Repeat:
in /usr/ports/security/clamav, make ; make install, then follow instructions.
>Fix:
One possible workaround is to make /var/tmp writable for the clamav user.
I'm not sure which is better - make the clamav user part of the 'wheel' group
or make /var/tmp world writable.
A real fix would be to make the port handle this automagically, or at least
add something in a README or message about /var/tmp permissions.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list