Eternius wrote: > > Wiggins D Anconia wrote: > > >>Nilay Puri wrote: > >> > > > > > >>if u use an OS like linux (which will not write things imediately to > >>disc) this forces it to do so. > >> > > > > > > That is misleading and not necessarily true. It tells Perl to unbuffer > > the I/O but not the OS. The OS decides what will and won't get written > > to disc, based on kernel settings, harddrive settings, etc. Don't > > confuse the two... > > > > http://danconia.org > > > > Then I guess, I didn't understand it myself.
Disk drives have their own cache. CPUs now have their own first, second and third level memory caching. The file system is likely to have two caches of its own per file, and the language at least one more in RAM. Disabling output buffering in Perl should be seen as a nicety that helps debugging, but not much else. Only a hardware solution can guard against losing power at the wrong time. Rob -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
