> I guess we can agree to disagree, I would think that having one's "firewall" spread out over (snip)
fair enuf. i just choose to have app scope/function defined in the app. AND, not having a gaggle of fw configs lying around ... my 'env' is pretty simple -- one router/fw at network edge that gets TLC. per-app-instance configs, as self-contained as possible, so that when i'm, e.g., "worrying" abt clamav, i worry JUST about clamav ... NOT clamav & the local fw AND its interactions with other fws etc etc. personal choice. understood. moving on :-) which leaves me with the STILL unanswered "can it be done 'just' in/with clad.conf ?" ... at this juncture, i think the answer -- no matter my wish/preference -- is "no". :-/ > You're welcome. I'm just sharing the benefit of my experiences. My > opinion is worth exactly what you paid for it, ya know. ;) heh. what ?! you didn't get the check? it's in the mail. honest! it's HUUUUGE. I inherited the money from my recently-deceased uncle in Nigeria & ... ;-p _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
