Fixed daemonization when using kqueue/kevent. Now the server initialization is perfor...

[redis.git] / redis.conf

diff --git a/redis.conf b/redis.conf
index 610049ef9557c65a016c5a2ee7e2299898f6b9a3..72cba4ab2a7a590bf857dec7363f426e5a531667 100644 (file)
--- a/redis.conf
+++ b/redis.conf
@@ -121,10 +121,12 @@ 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 yes
+appendonly no
 
-# The fsync() calls tells the Operating System to actually write data on disk
+# 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.
 #
@@ -134,12 +136,15 @@ databases 16
 # 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 "no" since it's faster and anyway safer than snapshots from
-# the point of view of durability of the latest records modified.
+# 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 no
-# appendfsync always
+appendfsync always
 # appendfsync everysec
+# appendfsync no
 
 ############################### ADVANCED CONFIG ###############################