Carsten Otte wrote:
But Dominic, it has nothing to do with a journaled file system. The fact
that you stopped the application and sync'd the file system (equivalent to
unmounting it) is what makes it work, not the file system implementation.
Wrong. Due to caching, as correctly described by David Boyes, the
system may change on-disk content even when the application is not
running. Example: the syslogd generates a "mark" every 20 minutes.
syslogd's mark message has nothing to do with caching.
According to its man page, "sync forces changed blocks to disk, updates
the super block."
If you don't believe (or trust) that, then "mount -o remount" is your
friend.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
