Well, Symantec's client AV does realtime file-system scanning, but I
don't think it touches network traffic directly.
-----Original Message-----
From: Jonathan Biggar [mailto:jon@xxxxxxxxxxxxxx]
Sent: Monday, December 13, 2004 3:00 PM
To: Jason McClellan
Cc: perforce-user@xxxxxxxxxxxx
Subject: Re: [p4] Antivirus compatibility
Actually, that's not enough. You also need to make sure that any AV
filtering isn't done on the perforce client/server network protocol
exchanges. Otherwise you will get at best failed checkin/checkouts or
at worst corrupted perforce data.
Jason McClellan wrote:
>
> Thanks alot, Paul - that's what I was hoping. Server av exclusions
> are no problem
>
> Jason
>
> ----------------------------------------------------------------------
> --
> *From:* Paul Goffin [mailto:Paul.Goffin@xxxxxxxxxxxxxx]
> *Sent:* Monday, December 13, 2004 2:26 PM
> *To:* Jason McClellan; perforce-user@xxxxxxxxxxxx
> *Subject:* RE: [p4] Antivirus compatibility
>
> The issue is on the server only - the difficulty is that the virus
> checker can hold Perforce's database files locked for long periods
> (they become very large files) and this can drastically reduce
> performance and can cause times outs and so on.
>
> It's not a problem as long as you can configure the virus checker
> running on the server to ignore your P4ROOT directory.
--
Jon Biggar
Floorboard Software
jon@xxxxxxxxxxxxxx
jon@xxxxxxxxxx
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|