Re: wierd behaviour...
Jerome Etienne (jetienne@ifhamy.insa-lyon.fr)
Tue, 25 Feb 1997 18:27:16 +0100 (MET)
> On Tue, 25 Feb 1997, Jerome Etienne wrote:
> > > hi, i compile a c program
> > > main(){ fork();} /* no while to do several fork(). so its safe */
> > > /* no danger for your computer */
> > > so when i run it, my harddrive is running. Even if i run it several times
> > > to be sure sure that the code is in buffers. i don't understand why my
> > > hd need to write or read something during or after this little program.
> > >
> > > any explaination ?
> >
> > some answers me by email to suggest it is a atime update but i don't think
> > so. because "main(){}" doesn't read/write anything. any other classic
> > unix tools like ls, ping etc... don't read/write anything immediatly on
> > my hd...
>
> Who was talking about 'main'? How about the file that contains
> that program, ld.so, libc, and so on?
re read my first reply. and try to explain why "/bin/echo bla"(or other
tools) doesn't read anything from hd. and why "main(){fork();}" does.
--
Jerome Etienne <jetienne at ifhamy.insa-lyon.fr> aim: being human, not ape
aim: Learn the core knowledge and deduce from it and the current context.
Thou shalt not make a machine in the likeness of a human mind. --- f.herbert