Bugs item #2686300, was opened at 2009-03-13 16:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111005&aid=2686300&group_id=11005
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Program Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: nedit doesn't fsync/fdatasync when saving Initial Comment: nedit, when the user instructs it to save, should perform a fdatasync or fsync on the file descriptor immediately after the write calls. Firstly, because POSIX gives no guarantee of when the file will reach disk otherwise. Secondly, because some errors during writeback can only be caught then. For example, AFS defers all writes until the file is fsynced or closed. Checking the error code from fsync/fdatasync is the only way to detect resulting errors. I believe nedit isn't doing either fsync or fdatasync, because strace doesn't show them being made. John Karp [email protected] NEdit 5.5 Sep 30, 2004 Built on: Linux, 386, GNU C Built at: Feb 18 2008, 11:00:48 With Motif: 2.3.0 [@(#)Motif Version 2.3.0] Running Motif: 2.3 [unknown] Server: The X.Org Foundation 10300000 Visual: 24-bit TrueColor (ID 0x21, Default) Locale: en_US.UTF-8 Linux bouzouki 2.6.25.10 #4 Tue Jul 8 16:01:49 CDT 2008 i686 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111005&aid=2686300&group_id=11005 -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
