zero length bulk data reading fixed in loadAppendOnlyFile()

[redis.git] / redis.conf

diff --git a/redis.conf b/redis.conf
index fac5ba6054071730e2dc47f5431f3d960de96e88..72cba4ab2a7a590bf857dec7363f426e5a531667 100644 (file)
--- a/redis.conf
+++ b/redis.conf
@@ -121,8 +121,30 @@ databases 16
 # like (you have to comment the "save" statements above to disable the dumps).
 # Still if append only mode is enabled Redis will load the data from the
 # log file at startup ignoring the dump.rdb file.
+#
+# The name of the append only file is "appendonly.log"
+
+appendonly no
 
-# appendonly yes
+# The fsync() call tells the Operating System to actually write data on disk
+# instead to wait for more data in the output buffer. Some OS will really flush 
+# data on disk, some other OS will just try to do it ASAP.
+#
+# Redis supports three different modes:
+#
+# no: don't fsync, just let the OS flush the data when it wants. Faster.
+# always: fsync after every write to the append only log . Slow, Safest.
+# everysec: fsync only if one second passed since the last fsync. Compromise.
+#
+# The default is "always" that's the safer of the options. It's up to you to
+# understand if you can relax this to "everysec" that will fsync every second
+# or to "no" that will let the operating system flush the output buffer when
+# it want, for better performances (but if you can live with the idea of
+# some data loss consider the default persistence mode that's snapshotting).
+
+appendfsync always
+# appendfsync everysec
+# appendfsync no
 
 ############################### ADVANCED CONFIG ###############################