> > In brief, I am planning a large ClamAV deployment with varying > requirements. A few of the file servers will have their own instance of > clamd running locally. The remaining file servers will utilize (via > clamdscan and/or clamonacc) a remote TCP clamd daemon. >
afaik is clam not 'smart' and once your clamd is getting a new ip address the client will be unable to find it unless you restart also that. _______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
