diff options
| -rw-r--r-- | Contributors | 6 | ||||
| -rw-r--r-- | Hacks | 36 | ||||
| -rw-r--r-- | License | 297 | ||||
| -rw-r--r-- | Makefile | 57 | ||||
| -rw-r--r-- | README | 58 | ||||
| -rw-r--r-- | config.h.in | 64 | ||||
| -rw-r--r-- | configure.in | 19 | ||||
| -rw-r--r-- | docs/Makefile | 28 | ||||
| -rw-r--r-- | docs/fsync.1 | 66 | ||||
| -rw-r--r-- | fsync.c | 155 | ||||
| -rw-r--r-- | fsync.spec | 64 | ||||
| -rw-r--r-- | packaging/fsync.manifest | 5 | ||||
| -rw-r--r-- | packaging/fsync.spec | 43 |
13 files changed, 898 insertions, 0 deletions
diff --git a/Contributors b/Contributors new file mode 100644 index 0000000..f6c300c --- /dev/null +++ b/Contributors @@ -0,0 +1,6 @@ +Alain Williams <addw@phcomp.co.uk> +Primary Author + + +SCCS: @(#)Contributors 1.1 11/14/11 22:33:00 + @@ -0,0 +1,36 @@ + +addw: Thu 10 Sep 2009 12:51 +fsync.c:\tInitial Create. + +addw: Thu 10 Sep 2009 13:37 +fsync.c: Doesn't work on directories unless it is opened readonly + +addw: Mon 14 Nov 2011 22:20 +README:\tInitial Create. + +addw: Mon 14 Nov 2011 22:30 +fsync.1:\tInitial Create. + +addw: Mon 14 Nov 2011 22:30 +Makefile:\tInitial Create. + +addw: Mon 14 Nov 2011 22:33 +Contributors:\tInitial Create. + +addw: Mon 14 Nov 2011 22:37 +Makefile:\tInitial Create. + +addw: Mon 14 Nov 2011 22:38 +fsync.spec:\tInitial Create. + +addw: Mon 14 Nov 2011 22:45 +configure.in:\tInitial Create. + +addw: Mon 14 Nov 2011 22:46 +fsync.c: Include config.h + +addw: Mon 14 Nov 2011 22:48 +fsync.spec:\tInitial Create. + +addw: Mon 14 Nov 2011 22:48 +fsync.spec:\tInitial Create. @@ -0,0 +1,297 @@ +**** Licensing information **** + +Author: Alain D D Williams <addw@phcomp.co.uk> of +Parliament Hill Computers http://www.phcomp.co.uk. + +Copyright (C) the Author 2011. + +This software is released under the following license. +If you do not like the choices below you may attempt to negotiate another license with the author. + +**** GNU General Public License, Version 2, June 1991: + + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Software: Copyright (c) 2006 Alain D D Williams <addw@phcomp.co.uk> under this GPL. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + + +SCCS: @(#)License 1.1 11/14/11 12:28:23 + diff --git a/Makefile b/Makefile new file mode 100644 index 0000000..86b569b --- /dev/null +++ b/Makefile @@ -0,0 +1,57 @@ +# Makefile for the fsync package +# Copyright 2008 Parliament Hill Computers Ltd, all rights reserved. +# Author: ADDW December 2008 +# SCCS: @(#)Makefile 1.1 11/14/11 22:37:38 + +# The distribution version # comes from the SCCS id of the spec file. +# To do a test build run something like: +# make VERSION=test dist +# If the spec file is out on delta, go: +# make VERSION=1.1 dist + +PACKAGE=fsync +PROGS=fsync +SOURCES=fsync.c +BUILDPROGS= +SUBDIRS=docs +CONFIGS=configure.in config.h.in +DOCS=README Contributors License Hacks + +SPECFILE=$(PACKAGE).spec +VERSION := $(shell sed -ne '/^%define \+version \+/s///p' $(SPECFILE) ) +DESTDIR=/usr/local +BINDIR=$(DESTDIR)/bin/ +DOCDIR=$(DESTDIR)/share/doc/$(PACKAGE)-$(VERSION) +MAKEFILE=Makefile +BUILDFILES=$(SPECFILE) $(MAKEFILE) + +# Default target is to make the programs - not install +progs: $(PROGS) + +# Create directories then copy in script and documentation: +install: $(PROGS) + install -d $(BINDIR) $(DOCDIR) + install -p $(PROGS) $(BINDIR) + install -p -m 644 $(DOCS) $(DOCDIR) + for d in $(SUBDIRS); do make -C $$d install ; done + +# Create a tar file for distribution +dist: $(PACKAGE)-$(VERSION).tar.gz + +# The tar file for distribution: +$(PACKAGE)-$(VERSION).tar.gz: $(DOCS) $(BUILDPROGS) $(BUILDFILES) $(SOURCES) $(CONFIGS) + mkdir -p .BuildDist/$(PACKAGE)-$(VERSION) + cp -al $^ .BuildDist/$(PACKAGE)-$(VERSION) + for d in $(SUBDIRS); do make -C $$d VERSION=$(VERSION) copy-dist ; done + cd .BuildDist && tar czf ../$@ $(PACKAGE)-$(VERSION) + rm -rf .BuildDist/$(PACKAGE)-$(VERSION) + +cleandist: + rm -f $(PACKAGE)-$(VERSION).tar.gz + +clean: cleandist + for d in $(SUBDIRS); do make -C $$d VERSION=$(VERSION) clean ; done + +fsync: fsync.c config.h + +# end @@ -0,0 +1,58 @@ +What is this about ? +******************** + +Flush a specific file to disk but not necessarily the whole disk and every disk on the system. + +The point is that if you use the 'sync' it will schedule a flush for every disk on the system, +this can take a long time -- this allows you to flush just one file. +This allows you to just flush the data (ie not the metadata). + +Why: if system service is interrupted at the wrong moment (eg crash or power fail) +what is in the filesystem on reboot might inconsistent. This is especially +true with files in the process of being updated; eg where a modified copy of a +file is created that is then renamed over the original. +Flushing blocks to disk can help to avoid problems. +This is a command line interface to the fsync(2) and fdatasync(2) system calls. + +See: + http://lwn.net/Articles/351422/ + +Installation +************ + +Compile and install somewhere, this is a single simple program. + +Keeping up to date +****************** + +You may find newer versions of this software at: + + http://www.phcomp.co.uk/downloads.php + +Where you will also find references to email lists that relate to this software. + + +Contributing +************ + +Fsync is free software (see the license). Free software grows and becomes more +powerful and useful as those who gain by using it contribute their changes back +to the original author. + +Contributions to this software are welcome. Please email the author the following: + +* your name & email address +* your affiliation (company/institute/...) if any +* the code +* documentation +* a statement that you are legally able to release the code and documentation +* a statement transfering copyright to the Author below giving permission that it + may be redistributed as part of UserAdmin under an appropriate license + +Contributions will be acknowledged in the Contributors file that accompanies this +software. If you do not want to be acknowledged please make that clear. + +The author will be pleased to receive your comments, good or bad. + + +SCCS: @(#)README 1.1 11/14/11 22:20:17 diff --git a/config.h.in b/config.h.in new file mode 100644 index 0000000..7a1904c --- /dev/null +++ b/config.h.in @@ -0,0 +1,64 @@ +/* config.h.in. Generated from configure.in by autoheader. */ + +/* Define to 1 if you have the <errno.h> header file. */ +#undef HAVE_ERRNO_H + +/* Define to 1 if you have the <fcntl.h> header file. */ +#undef HAVE_FCNTL_H + +/* Define to 1 if you have the `fdatasync' function. */ +#undef HAVE_FDATASYNC + +/* Define to 1 if you have the `fsync' function. */ +#undef HAVE_FSYNC + +/* Define to 1 if you have the <inttypes.h> header file. */ +#undef HAVE_INTTYPES_H + +/* Define to 1 if you have the <memory.h> header file. */ +#undef HAVE_MEMORY_H + +/* Define to 1 if you have the `open' function. */ +#undef HAVE_OPEN + +/* Define to 1 if you have the <stdint.h> header file. */ +#undef HAVE_STDINT_H + +/* Define to 1 if you have the <stdlib.h> header file. */ +#undef HAVE_STDLIB_H + +/* Define to 1 if you have the `strerror' function. */ +#undef HAVE_STRERROR + +/* Define to 1 if you have the <strings.h> header file. */ +#undef HAVE_STRINGS_H + +/* Define to 1 if you have the <string.h> header file. */ +#undef HAVE_STRING_H + +/* Define to 1 if you have the <sys/stat.h> header file. */ +#undef HAVE_SYS_STAT_H + +/* Define to 1 if you have the <sys/types.h> header file. */ +#undef HAVE_SYS_TYPES_H + +/* Define to 1 if you have the <unistd.h> header file. */ +#undef HAVE_UNISTD_H + +/* Define to the address where bug reports for this package should be sent. */ +#undef PACKAGE_BUGREPORT + +/* Define to the full name of this package. */ +#undef PACKAGE_NAME + +/* Define to the full name and version of this package. */ +#undef PACKAGE_STRING + +/* Define to the one symbol short name of this package. */ +#undef PACKAGE_TARNAME + +/* Define to the version of this package. */ +#undef PACKAGE_VERSION + +/* Define to 1 if you have the ANSI C header files. */ +#undef STDC_HEADERS diff --git a/configure.in b/configure.in new file mode 100644 index 0000000..671b3ce --- /dev/null +++ b/configure.in @@ -0,0 +1,19 @@ +# Process this file with autoconf to produce a configure script. +# SCCS: @(#)configure.in 1.1 11/14/11 22:45:39 +AC_PREREQ(2.59) +AC_INIT([fsync], 1.1, [addw@phcomp.co.uk]) +AC_CONFIG_SRCDIR([fsync.c]) +AC_CONFIG_HEADER([config.h]) + +# Checks for programs. +AC_PROG_CC + +# Checks for libraries. + +# Checks for header files. +AC_HEADER_STDC +AC_CHECK_HEADERS([fcntl.h stdlib.h string.h strings.h unistd.h errno.h sys/types.h sys/stat.h]) + +# Checks for library functions. +AC_CHECK_FUNCS([strerror open fdatasync fsync]) +AC_OUTPUT diff --git a/docs/Makefile b/docs/Makefile new file mode 100644 index 0000000..2ccf9f6 --- /dev/null +++ b/docs/Makefile @@ -0,0 +1,28 @@ +# Makefile for the fsync package +# Copyright 2011 Parliament Hill Computers Ltd, all rights reserved. +# Author: ADDW November 2011 +# SCCS: @(#)Makefile 1.1 11/14/11 22:30:30 + +# Makefile for docs directory + +MANFILES=fsync.1 +PACKAGE=fsync +MANDIR=$(DESTDIR)/share/man/man1 + +DISTDIR=../.BuildDist/$(PACKAGE)-$(VERSION)/docs + +all: + : + +clean: + : + +install: + mkdir -p $(MANDIR) + install -m 644 $(MANFILES) $(MANDIR) + +copy-dist: Makefile $(MANFILES) + mkdir $(DISTDIR) + cp -al $^ $(DISTDIR) + +# end diff --git a/docs/fsync.1 b/docs/fsync.1 new file mode 100644 index 0000000..5a9cd1a --- /dev/null +++ b/docs/fsync.1 @@ -0,0 +1,66 @@ +.TH fsync "1" "Nov 2011" "fsync 1.1" "User Commands" +.\" +.SH NAME +fsync \- Flush a file to disk +.\" +.SH SYNOPSIS +.B fsync +[\fIoption\fR]... +.\" +.SH DESCRIPTION +.\" +.PP +\fIfsync\fR will flush a specific file to disk without necessarily flushing the whole disk and every disk on the system. +.PP +The point is that if you use the '\fIsync\fR' it will schedule a flush for every disk on the system, +this can take a long time -- this allows you to flush just one file. +This allows you to just flush the data (ie not the metadata). +.PP +Why: if system service is interrupted at the wrong moment (eg crash or power fail) +what is in the filesystem on reboot might inconsistent. This is especially +true with files in the process of being updated; eg where a modified copy of a +file is created that is then renamed over the original. +Flushing blocks to disk can help to avoid problems. +.PP +This is a command line interface to the \fIfsync(2)\fR and \fIfdatasync(2)\fR system calls. +.PP +See: +.nf +http://lwn.net/Articles/351422/ +.fi +.\" +.SH OPTIONS +.\" +.PP +.TP +\fB-d\fR +do not flush metadata (fdatasync()). +.TP +\fB-\q\fR +quiet: do not report errors (eg file open fails), still set exit code. +.TP +\fB-v\fR +Verbose - send log messages to stderr. +.TP +\fB-x\fR +eXplain, gives a usage message. +.\" +.SH EXAMPLE +.\" +.PP +.nf +fsync /etc/passwd +.fi +.\" +.PP +.\" +.SH AUTHOR +Written by Alain Williams <addw@phcomp.co.uk> +.\" +.SH COPYRIGHT +Copyright \(co Parliament Hill Computers +.br +This is free software. You may redistribute copies of it under the terms of +the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. +There is NO WARRANTY, to the extent permitted by law. +.\" SCCS: @(#)fsync.1 1.1 11/14/11 22:30:30 @@ -0,0 +1,155 @@ +/* /\ + * / \ (C) Copyright 2009 Parliament Hill Computers Ltd. + * \ / All rights reserved. + * \/ + * . Author: Alain Williams, <addw@phcomp.co.uk> 2009 + * . + * . SCCS: @(#)fsync.c 1.3 11/14/11 22:46:01 + * . + * + */ + +#include "config.h" + +#include <stdio.h> +#include <sys/types.h> +#include <string.h> +#include <errno.h> +#include <stdlib.h> +#include <unistd.h> +#include <sys/stat.h> +#include <fcntl.h> + + +extern int optind; +extern char* optarg; + +char* progname; /* What this program is called - name of binary */ +int exit_c; /* Exit status to return to O/S */ +int datasync; /* Use fdatasync */ +int quiet; /* Do not report errors */ +int verbose; /* Chatty mode */ +char* flushname; /* Name of how we flush */ +int (*flushfn)(int); /* Pointer to system call to use */ + +/* Usage message. + */ +char* usagem[] = { + "Ensure that named files are flushed to disk", + "Usage: %s [options] file ...", + "-d do not flush metadata (fdatasync())", + "-q do not report errors (eg file open fails), still set exit code", + "-v verbose", + "-x eXplain", + "Version: 1.3 11/14/11", + (char*)NULL /* Must end the list */ +}; + +/* Functions defined in this module, in alphabetic order */ +void read_opts(int argc, char* argv[]); +void usage(int exitc); +void process(const char* file); + +int main(int argc, char* argv[]) +{ + read_opts(argc, argv); + + flushname = datasync ? "fdatasync" : "fsync"; + flushfn = datasync ? fdatasync : fsync; + + argv += optind; + while(*argv) + process(*argv++); + + return(exit_c); +} + +/* Interpret '-' arguments -options. + * If there is an error in the arguments, print the options list and exit. + */ +void read_opts(int argc, char* argv[]) +{ + register int c; + register int error; + + error = 0; + progname = argv[0]; + + while((c = getopt(argc, argv, "dqvx")) != EOF) + switch(c) { + case 'd': /* Use fdatasync() */ + datasync = 1; + break; + case 'q': /* Quiet */ + quiet = 1; + break; + case 'v': /* Verbose */ + verbose = 1; + break; + case 'x': /* eXplain */ + usage(0); + /*NOTREACHED*/ + case '?': + error = 1; + break; + } + + if(error) + usage(2); +} + +/* Output a usage message and end with exit status exitc. + */ +void usage(int exitc) +{ + register char** mes; + + for(mes = usagem; *mes != (char*)NULL; mes++) { + (void) fprintf(stderr, *mes, progname); + fputc('\n', stderr); + } + + exit(exitc); + /*NOTREACHED*/ +} + +/* Flush the named file to disk -- use the fsync or fdatasync system call + */ +void process(const char* file) +{ + int fd; + + if(verbose) + fprintf(stderr, "%s: about to %s '%s'\n", progname, + flushname, file); + + /* Need to open read/write for fsync to work. + * But we can't open directories to write to, so try to open one read only. + * Linux (2.6.18 anyway) doesn't seem to check that the fd to fsync is for + * writing - but that is what the manual says it must be. + */ + if((fd = open(file, O_WRONLY)) == -1 && + (errno == EISDIR && (fd = open(file, O_RDONLY)) == -1)) { + if( ! quiet) + fprintf(stderr, "%s: Cannot open '%s' as: %s\n", progname, file, + strerror(errno)); + exit_c = 1; + return; + } + + if((*flushfn)(fd) == -1) { + if( ! quiet) + fprintf(stderr, "%s: Cannot %s '%s' as: %s\n", progname, flushname, file, + strerror(errno)); + exit_c = 1; + } + + if(close(fd)) { + if( ! quiet) + fprintf(stderr, "%s: Error on close of '%s' as: %s\n", progname, file, + strerror(errno)); + exit_c = 1; + } +} + +/* end */ diff --git a/fsync.spec b/fsync.spec new file mode 100644 index 0000000..b0f6373 --- /dev/null +++ b/fsync.spec @@ -0,0 +1,64 @@ +# RPM specfile for the fsync package +# Copyright 2009 Parliament Hill Computers Ltd, all rights reserved. +# Author: ADDW September 2009 +# SCCS: @(#)fsync.spec 1.1 11/14/11 22:48:57 +# Note that the version number (1.1 - SCCS %-I-% (sans -)) of this file defines the package version #. It is used in the Makefile. + +%define name fsync +%define version 1.1 +%define release 1.1 + +Summary: synchronize file's in-core state with storage device +Name: %{name} +Version: %{version} +Release: %{release} +Source: http://www.phcomp.co.uk/Downloads/fsync-%{version}.tar.gz +Vendor: %{vendor} +URL: %{phcl_url} + +License: GPL + +Packager: %{packager} + +Group: Applications/System +BuildRoot: %{_builddir}/%{name}-root +BuildRequires: make sed gcc autoconf + +# This is only needed if we want to build a relocatable RPM: +#Prefix: %{_prefix} + +%description +If system service is interrupted at the wrong moment (eg crash or power fail) +what is in the filesystem on reboot might inconsistent. This is especially +true with files in the process of being updated; eg where a modified copy of a +file is created that is then renamed over the original. +Flushing blocks to disk can help to avoid problems. +This is a command line interface to the fsync(2) and fdatasync(2) system calls. + +%prep +%setup -q + +%build +autoconf +%configure +make + +%install +rm -rf $RPM_BUILD_ROOT +make DESTDIR=$RPM_BUILD_ROOT%{_prefix} VERSION=%{version} install + +%clean +rm -rf $RPM_BUILD_ROOT + +%files +%defattr(-,root,root) +%{_bindir}/fsync +%doc README Contributors License Hacks +%{_mandir}/man*/fsync.* + +%changelog +* Mon Nov 11 2011 Alain Williams <addw@phcomp.co.uk> +- Write man page & other bits for proper release +* Thu Sep 10 2009 Alain Williams <addw@phcomp.co.uk> +- First time as an RPM + diff --git a/packaging/fsync.manifest b/packaging/fsync.manifest new file mode 100644 index 0000000..75b0fa5 --- /dev/null +++ b/packaging/fsync.manifest @@ -0,0 +1,5 @@ +<manifest> + <request> + <domain name="_"/> + </request> +</manifest> diff --git a/packaging/fsync.spec b/packaging/fsync.spec new file mode 100644 index 0000000..5768d2e --- /dev/null +++ b/packaging/fsync.spec @@ -0,0 +1,43 @@ +# RPM specfile for the fsync package +# Copyright 2009 Parliament Hill Computers Ltd, all rights reserved. +# Author: ADDW September 2009 +# SCCS: @(#)fsync.spec 1.1 11/14/11 22:48:57 +# Note that the version number (1.1 - SCCS %-I-% (sans -)) of this file defines the package version #. It is used in the Makefile. + +Summary: synchronize file's in-core state with storage device +Name: fsync +Version: 1.1 +Release: 1 +Source: http://www.phcomp.co.uk/Downloads/fsync-%{version}.tar.gz +Source1001: %{name}.manifest +License: GPL +Group: Applications/System +BuildRequires: autoconf + +%description +If system service is interrupted at the wrong moment (eg crash or power fail) +what is in the filesystem on reboot might inconsistent. This is especially +true with files in the process of being updated; eg where a modified copy of a +file is created that is then renamed over the original. +Flushing blocks to disk can help to avoid problems. +This is a command line interface to the fsync(2) and fdatasync(2) system calls. + +%prep +%setup -q + +%build +cp %{SOURCE1001} . +autoconf +%configure +make + +%install +make DESTDIR=$RPM_BUILD_ROOT%{_prefix} VERSION=%{version} install + +%remove_docs +%files +%defattr(-,root,root) +%manifest %{name}.manifest +%{_bindir}/fsync +%doc License + |