Date: Sat, 24 Dec 2011 13:21:52 +0100 From: Roland Smith <rsmith@xs4all.nl> To: Da Rock <freebsd-questions@herveybayaustralia.com.au> Cc: freebsd-questions@freebsd.org Subject: Re: PolicyKit confusion Message-ID: <20111224122152.GB40495@slackbox.erewhon.net> In-Reply-To: <4EF532F2.6000303@herveybayaustralia.com.au> References: <4EF4010B.5040704@herveybayaustralia.com.au> <20111223142252.GC660@slackbox.erewhon.net> <4EF49DDB.2060609@herveybayaustralia.com.au> <20111223173139.GA7648@slackbox.erewhon.net> <4EF4FAAA.1020603@herveybayaustralia.com.au> <20111223232102.GA20961@slackbox.erewhon.net> <4EF51572.4060507@herveybayaustralia.com.au> <20111224013458.GA25515@slackbox.erewhon.net> <4EF532F2.6000303@herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--l76fUT7nc3MelDdI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 24, 2011 at 12:03:30PM +1000, Da Rock wrote: > > might render the application performing it unresponsive during that tim= e. > Bingo! Thats exactly the issue. Taking a look at FUSE I can see there=20 > are calls that FUSE_FSYNC which I would say is the closest to what is=20 > needed. The question is are they implemented in say fuse_msdosfs (I may= =20 > have just barfed that, but you get the idea) and maybe some others?=20 Use the source, Luke! ;-) > That=20 > way the filesystem is treated as normal, the app writes and can return=20 > happily, and FUSE takes the responsibility to ensure the data continues= =20 > to write until finished instead of holding it in buffer for an=20 > indeterminate period leaving the user thinking alls well (ergo, the=20 > light continues flashing). I'm not sure how long the defaults waits are. Normally the systems tries to cluster writes sequenstially for improved throughput. But I'm guessing we're talking about fractions of seconds at most. Again, browsing the source might be useful. Also chapter 6 of "The Design and Implementation of the FreeBSD operating system" might provide insight.=20 > Failing that, how does one ensure data is synced manually? Is there a=20 > call that could be run periodically at a shorter, more regular intervals? The sync(1) program flushes the system's write cache. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --l76fUT7nc3MelDdI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk71w+AACgkQEnfvsMMhpyW6zACcCyjGANJo2mR9ML9txO0OixrW R8AAn1BIGX+ZvwB65Qw6v5tnzXieEca4 =w+F3 -----END PGP SIGNATURE----- --l76fUT7nc3MelDdI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111224122152.GB40495>