Josh Tolbert wrote:
On Thu, Mar 23, 2006 at 09:07:18PM -0800, Dennis Peterson wrote:
It does as you say. You may get around it using a tool like tripwire to
limit your scan to the files of interest. Really, scanning every file on
a system disk is draconian. User space is another thing entirely
Hello folks,
So, since Apple's 2006-001 update causes McAfee's Virex to break
(segfaults after an hour or so of operation) on our OS X Server
machine (which 2006-002, even v1.1 don't fix) and I'm required by
powers greater than me to use a virus scanner on the machine, I
started looking in to
Hello folks,
Does anyone have any ideas or a work-around? I'd prefer a good fix
with reasons instead of a hack. The command I'm using right now is:
I think I'd be inclined to run tripwire on the system and then scan only
the changed files (in system space). Doing a brute force virus scan
On Thu, Mar 23, 2006 at 12:16:33PM -0800, Dennis Peterson wrote:
I think I'd be inclined to run tripwire on the system and then scan only
the changed files (in system space). Doing a brute force virus scan of
the entire system seems a bit inefficient.
dp
I'm not opposed to the idea, but
On Thu, Mar 23, 2006 at 12:16:33PM -0800, Dennis Peterson wrote:
I think I'd be inclined to run tripwire on the system and then scan only
the changed files (in system space). Doing a brute force virus scan of
the entire system seems a bit inefficient.
dp
I'm not opposed to the
Josh Tolbert wrote:
On Thu, Mar 23, 2006 at 12:31:11PM -0800, Dennis Peterson wrote:
I'm testing your method now, but it's still running so I don't have an answer.
dp
Thanks for taking a look. I only have my one little OS X Server machine here,
and I didn't set it up...
Josh
It does as
On Thu, Mar 23, 2006 at 09:07:18PM -0800, Dennis Peterson wrote:
It does as you say. You may get around it using a tool like tripwire to
limit your scan to the files of interest. Really, scanning every file on
a system disk is draconian. User space is another thing entirely and
your own
