On Tue, 2004-02-10 at 15:39, Kenneth Porter wrote: > The ClamAV RPM installs with the assumption that the services will run as > user "clamav". MD's RPM assumes that it will run as user "defang". Changing > ClamAV to comply requires changing ownership of a couple of directories and > editing the /etc/clamav.conf file. > > It seems to me that it would be simpler if MD made its directories and > files group-readable (using group "defang"); one could then add clamav to > the defang group. The MD RPM could check for the existence of the clamav > user and add it to the defang group. > > Is there a problem with setting things up that way that I'm not seeing? Any > pointers on where to tweak MD to test it?
You won't run into a problem with the clamd, but I ran into a problem with freshclam. freshclam update clamd with the --with-notify option. I tried various fixes that didn't work. I wound up rebuilding from source with the user defang. -- Stephen L Johnson [EMAIL PROTECTED] Unix Systems Administrator [EMAIL PROTECTED] Department of Information Systems State of Arkansas 501-682-4339 _______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
