about summary refs log tree commit homepage
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2010-04-05 23:18:24 -0700
committerEric Wong <normalperson@yhbt.net>2010-04-05 23:18:24 -0700
commit5ead9a1bad9753faca636f0e0d048bb6a300f65a (patch)
tree8f838cb59698de83351caa9769805ccd0abb6755
parent2b5903dea28b6f8181e69429d45b80433dc72522 (diff)
downloadpcu-5ead9a1bad9753faca636f0e0d048bb6a300f65a.tar.gz
add pcu-fsync(1) manpage
-rw-r--r--pcu-fsync.1.txt42
1 files changed, 42 insertions, 0 deletions
diff --git a/pcu-fsync.1.txt b/pcu-fsync.1.txt
new file mode 100644
index 0000000..958f0d3
--- /dev/null
+++ b/pcu-fsync.1.txt
@@ -0,0 +1,42 @@
+% PCU-FSYNC(1) Page Cache Utilities Manual
+% Eric Wong <normalperson@yhbt.net>
+% Jan 26, 2010
+
+# NAME
+pcu-fsync - synchronizes a files in-core state with storage device
+
+# SYNOPSIS
+pcu-fsync [-D] [-d] FILE...
+
+# DESCRIPTION
+A command-line interface to the fsync(2) and fdatasync(2) system calls
+to flush modified buffers for a given file to the underlying storage device.
+This is useful for explicitly flushing files to the storage device when
+using applications that fail to explicitly do so.
+
+# OPTIONS
+-D
+:   Flush the directory containing the file as well as the file
+    itself.  This is useful and needed if the file was recently
+    rename(2)-ed or created.
+
+-d
+:   Flush data (but not metadata) using fdatasync(2).  This is for
+    special cases where applications do not require the performance
+    overhead of flushing metadata to the storage device.
+
+# OUTPUT
+Errors only.
+
+# ENVIRONMENT
+None.
+
+# SEE ALSO
+[`fsync`(2)][1]
+[`fdatasync`(2)][2]
+
+# BUGS
+None known. Email <pcu@librelist.com> if you find any.
+
+[1]: http://kernel.org/doc/man-pages/online/pages/man2/fsync.2.html
+[2]: http://kernel.org/doc/man-pages/online/pages/man2/fdatasync.2.html