Carlos E. R. wrote: > > The Monday 2007-07-02 at 17:49 -0700, joe wrote: > >> That would be a messy hack, though I did install bind from a tarball once, >> when I had this same problem, or one very similar. What I found was a >> commercial antivirus program shipped with suse was doing something evil with >> capabilities, which prevented named from starting. I nuked that prog and all >> has been well ever since. IIRC it was H+BEDV AntiVir. > > That would be because you installed the kernel module. The program itself > is safe.
Nope. I didn't "install" anything. Stock standard suse setup, all I did was allow antivir to start at boot. If a kernel module was loaded, it was automatic and default behavior. Since clamav works well for use, I never bothered to find out what it would take to make antivir safe. Joe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
