% sudo /bin/launchctl load /System/Library/LaunchDaemons/ much as you might want to believe that your Mac is nigh on invulnerable to viruses, trojans, malware and phishing-based attacks, this simply isn’t the case. % sudo /bin/launchctl unload /System/Library/LaunchDaemons/ % sudo /bin/launchctl load -w /System/Library/LaunchDaemons/ % sudo /bin/launchctl unload -w /System/Library/LaunchDaemons/ % sudo cp *.plist /System/Library/LaunchDaemons % sudo mv /usr/local/clamXav/etc/nf /usr/local/clamXav/etc/
UpdateLogFile /usr/local/clamXav/share/clamav/freshclam.log # Default: disabledUpdateLogFile /usr/local/clamXav/share/clamav/freshclam.log # Path to the log file (make sure it has proper permissions) usr/local/bin/freshclam -> /usr/local/clamXav/bin/freshclam usr/local/sbin/clamd -> /usr/local/clamXav/sbin/clamd % sudo chown root:wheel ~/Downloads/SourceCache/clamav Create and copy all the conf and plist files: This will use the clamav binaries that come with clamXav in /usr/local/clamXav/ġ. Notes on setting up ClamXav Sentry on OS X Server 10.6:īased mostly on "Updating ClamAV on OS X Server >= 10.5.5" from You could also do the same thing with binaries installed using MacPorts "port install clamav" in /opt/local. The main idea is change the configuration so that OS X Server uses the ClamXav binaries, and that the server handles all the freshclam updating details. I got this working along with ClamXav Sentry, and I'm posting my notes here in case it's useful to others or someone can suggest alternatives. One installation problem that arose was ClamXav [a free front-end to the clamav virus checker that comes pre-installed with OS X server. I recently migrated an OS X client setup to a new Mac Mini running OS X Server.
0 kommentar(er)
