Date: Sun, 17 Oct 2004 11:48:55 +0300 From: Henry Karpatskij <henkka@spheroid.info> To: "Haulmark, Chris" <chris@sigd.net> Cc: freebsd-ports@freebsd.org Subject: Re: Amavisd-new and clamav user/group permissions conflictions? Message-ID: <417231F7.1060009@spheroid.info> In-Reply-To: <6FC9F9894A9F8C49A722CF9F2132FC22021564CD@ms05.mailstreet2003.net> References: <6FC9F9894A9F8C49A722CF9F2132FC22021564CD@ms05.mailstreet2003.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Haulmark, Chris wrote: > I installed security/amavisd-new (2.1.2,1) and chose security/clamav (0.80.r4) > as my antivirus solution. I'm satisfied with that solution, too. > In the /usr/local/etc/clamd.conf, it had clamav as the default user for clamd > to be running under. /usr/local/etc/amavisd.conf shows vscan as the default > user. That's true, it also gave me some headache, but I solved it by running clamav on the vscan user. It was rather tricky, since I had to manually change all the file permissions after every clamav upgrade. Fortunately, nowadays there are few knobs in the clamav Makefile (named CLAMAVUSER and CLAMAVGROUP) which can be used to change the default user. Just add some pkgtools.conf MAKE_ARGS magic and change the default user set on /usr/local/etc/clamav.conf and it works like a charm. -- Henry Karpatskij <henkka@spheroid.info> http://spheroid.info/ HK1203-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?417231F7.1060009>