On Thu, 26 Apr 2007 [EMAIL PROTECTED] wrote:
> > >>> On Tue, 24 Apr 2007 [EMAIL PROTECTED] wrote:
> > >>> We are serving up a virus .dat file to mail relays via AFS
> > >>> readonly. The file is periodically updated, the volume where it
> > >>> lives is re-released hourly whether update occured or
On Thu, 26 Apr 2007, Derrick J Brashear wrote:
> On Thu, 26 Apr 2007 [EMAIL PROTECTED] wrote:
>
> > On Wed, 25 Apr 2007, Derrick J Brashear wrote:
> >
> >> On Tue, 24 Apr 2007 [EMAIL PROTECTED] wrote:
> >>
> >>> We are serving up a virus .dat file to mail relays via AFS readonly.
> >>> The file is
On Wed, 25 Apr 2007, Derrick J Brashear wrote:
> On Tue, 24 Apr 2007 [EMAIL PROTECTED] wrote:
>
> > We are serving up a virus .dat file to mail relays via AFS readonly.
> > The file is periodically updated, the volume where it lives is re-released
> > hourly whether update occured or not. Read ac
We are serving up a virus .dat file to mail relays via AFS readonly.
The file is periodically updated, the volume where it lives is re-released
hourly whether update occured or not. Read activity is constant.
When vos release occurs, the fileserver logs a message like this:
Mon Apr 23 17:04:28 2
I'm still running v3.5 IBM/Transarc database servers as that's the last
version for which we have sources. The good news is that the XDR patches
easily apply so I'll be set for this particular event as soon as we've
completed testing and deploy the new build. OTOH, back-porting patches
isn't a l
