On 9/20/2014 7:56 AM, Eric Shubert wrote: > On 09/19/2014 10:35 PM, Eric Broch wrote: >> On 9/19/2014 8:42 PM, Eric Shubert wrote: >>> On 09/19/2014 05:33 PM, Eric Broch wrote: >>>> On 9/19/2014 6:01 PM, Eric Shubert wrote: >>>>> I'd say that's very likely to be the cause. Any errors involved with >>>>> scanning can cause a soft reject like this. >>>>> >>>> Any ideas why a tmp file/dir could not be created >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: >>>> [email protected] >>>> >>>> >>> >>> My best guess would be that the filesystem filled up momentarily. >>> >>> Perhaps it's on a network connection that was unavailable? >>> Permissions? >>> >> The files system is the /tmp directory which is 10GB and is not on a >> network connection. The permissions on the /tmp are rwxrwxrwxt. I'm not >> sure if any of these are the problem. It's bothersome not to known what >> may be causing this. >> >> Anyway, if It happens again can clam be disabled by simply putting >> clam=no in the simcontrol file and rebuilding the cdb database? >> >> --------------------------------------------------------------------- > > Yes. > > I wonder if the gnome desktop programs might be a clue to this. You > might try going to runlevel 3 next time and see if that cures it. It's > entirely possible that something in gnome went bonkers writing to a > tmp file. > > BL, there appears to be something in your system that's not playing > nice with /tmp/. The only things I can think of that would prohibit > creating a local directory is space and permissions. > > clamav can be configured to use whatever other directory you want for > tmp, but I wouldn't go there except as a last resort, as it would make > upgrading a pain should any stock changes need to be made to clamd.conf. > I was running, for quite some time, wireshark-gnome. I wonder it that could be it.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
