On Thu, Oct 07, 1999 at 11:57:26AM +1000, a little birdie told me
that Peter Jeremy remarked
>
> How detailed should the man page be?
Exactly my query in writing this ;>
> If it stated "all file data will
> be written synchronously, but inodes where the only update is atime
> and free block bitmaps are written asynchronously", would that be any
> clearer to a user who didn't have a detailed understanding of UFS?
> If you would like it to say something different, write some patches
> and send them in as a PR (keeping in mind phk's recent e-mail about
> green bikesheds).
I'm still stewing on what should be with it; what we have works fine, if
being slightly inconsistent in an obscure way. I'm trolling for ideas on
whether well enough should be left alone (since there's obviously an
incredibly small percentage of people USING sync as a mountop), or
whether a footnote should be added somewhere (I lean toward mount(2)
instead of mount(8) myself, with a possible xref in mount(8)).
I'll see what I think of, and possibly have some diffs tomorrow.
> There should be fairly few writes to the root partition, so having
> these writes synchronous is not a big performance hit. On the other
> hand, there are probably a _lot_ of read accesses to devices in /dev
> and files in /bin (how many of your scripts begin #!/bin/sh?). Unless
> you specify NOATIME, each of these read accesses implies an atime
> update within the inode. Making these synchronous probably would
> be a big performance hit.
This is why I haven't screamed for them to be sync-tified...
--
Matthew Fuller (MF4839) | [EMAIL PROTECTED]
Unix Systems Administrator | [EMAIL PROTECTED]
Specializing in FreeBSD | http://www.over-yonder.net/
FutureSouth Communications | ISPHelp ISP Consulting
"The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
