On Jan 15, 2007, at 10:57 AM, Tomasz Kojm wrote:
Clamscan doesn't use that parameter. His issue is the system that
shared
out the file system(s) he'd like to scan did not share them out such
that user root could read them. The real problem is trying to scan
file
I disagree and am still sure he has passed --with-user=0 to the
configure
script when compiling ClamAV.
For what it's worth, it is entirely possible that the original poster
is using the version of ClamAV which ships with MacOS X as part of
the base system (seems to be v0.88.5). I can reproduce the error
message the OP saw by running clamscan or freshclam as root on a
stock MacOS X system, which would trip this code (in freshclam/
freshclam.c around line 100):
if(!geteuid()) {
if((user = getpwnam(unpuser)) == NULL) {
mprintf("@Can't get information about user %s.\n",
unpuser);
exit(60); /* this is critical problem, so we just exit
here */
}
...which appears to mean that the "DatabaseOwner" keyword is not set
to "clamav" in freshclam.conf, or similar with the "User" keyword for
clamd.conf. Since OS X also comes with a "clamav" user, uncommenting
those two lines in freshclam.conf or clamd.conf is enough to let
freshclam and clamscan work, at least in my quick testing.
--
-Chuck
PS: Note that MacOS X Server normally configures Postfix + amavisd +
clamscan if "SMTP Services" are enabled; freshclam will be run as a
daemon but clamd itself is not started.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
