> Instead of "junk", secure file systems mark it as needing to be
> zeroed. Perhaps instead of zeroing it ext3 simply marks it of zero
> length? Imagine, embedded in the junk are credit cards and passwords
> and you'll begin to understand why zero pages are kept "in-stock" (in
> memory) in
Geoff Kuenning wrote:
I can also see the possibility of some kernel or file system routine
waiting after you issue the close call so that it doesn't have to zero
the area where data is arriving. I.e. it might only zero the file beyond
the valid text AFTER some delay (5 seconds?) OR might wai
> As for the problem...the fact that you using 4.2, would seem
> to make the algorith
> open()
> write(whatever we have as history)
> close(set eof to where we are).
>
> What file system are you are? is it local or networked?
Local, ext3.
> one way for it to be zero is if the last bash exi
