HP3000-L Archives

October 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Scott McClellan <[log in to unmask]>
Reply To:
Scott McClellan <[log in to unmask]>
Date:
Thu, 8 Oct 1998 20:42:55 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Stan Sieler
> Sent: Thursday, October 08, 1998 5:57 PM
> To: [log in to unmask]
> Subject: Re: 5.5 PP 5 Information
>
>
> Hi,
>
> > Does anyone know, or is willing to speculate, if "trimming" files is
> > something to avoid until this patch to the patch is applied?
>
> I don't have details of the bug, but Scott M. said it was involved
> with the "fill_disc" routine ... a routine that isn't used
> by the trim operation.  I.e., a "trim" releases space beyond
> the EOF ... which doesn't require filling it with nulls/blanks.
>
> So...I wouldn't avoid a trim, based on what I've heard/read.

Actually, I take back what I said about "trimming", and I agree
with Stan. I wasn't thinking of releasing space *beyond* EOF, and
specifically I wasn't thinking that was what "trimming" meant.

I don't believe releasing space beyong EOF will cause the problem.

Thanks for pointing this out Stan...

ATOM RSS1 RSS2