2009/6/12 Denys Vlasenko <[email protected]>: > On Thu, Jun 11, 2009 at 1:07 PM, <[email protected]> wrote: >> From: Pekka Pessi <[email protected]> >> >> Issue fsync() system call on a file to ensure its buffers are synchronized >> with the backing storage. >> >> Signed-off-by: Alexander Shishkin <[email protected]> > > Please use CONFIG_WERROR. With CONFIG_WERROR=y: > > CC coreutils/fsync.o > cc1: warnings being treated as errors > coreutils/fsync.c: In function 'fsync_main': > coreutils/fsync.c:15: error: unused parameter 'argc' > make[1]: *** [coreutils/fsync.o] Error 1 > > I can fix it on my end and commit. I'll be right on it, no problem. Thanks for the catch.
> What about other concern - "applet creep"? > > I googled for it and it seems there is no such program on Linux yet. Walter suggests otherwise, but I indeed do not know of such a tool in linux. There might well be need for it and it might eventually show up somewhere around, say, mtd-tools. > Since you propose it, I'm curious what needs made you write it? > What is your use case? Is using sync really too much of an overkill > in your use case? Well, the one off the top of my head: * I have a ubifs partition (which is a nosync, which is as much advantage as pain) * I have a log file there (normally I wouldn't, but at the moment I'm debugging a case which requires information from this log) and I want it to be written back at some point. Basically, everything that I wouldn't want to lose to a power loss or a kernel crash no matter what. Regards, -- Alex _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
