From: fbrehm <fbrehm@samara.profitbricks.localdomain>
Date: Wed, 9 May 2012 08:11:11 +0000 (+0200)
Subject: committing changes in /etc after emerge run
X-Git-Url: https://git.uhu-banane.net/?a=commitdiff_plain;h=0c8ce232a1d485c1c4743548c6c356fd3eef7cd8;p=config%2Fsamara%2Fetc.git

committing changes in /etc after emerge run

Package changes:
---

diff --git a/.etckeeper b/.etckeeper
index 1800863..fc535f8 100755
--- a/.etckeeper
+++ b/.etckeeper
@@ -1327,7 +1327,6 @@ maybe chmod 0755 './nas'
 maybe chmod 0444 './nas/nasd.conf'
 maybe chmod 0644 './netconfig'
 maybe chmod 0644 './networks'
-maybe chmod 0644 './nilfs_cleanerd.conf'
 maybe chmod 0644 './nscd.conf'
 maybe chmod 0644 './nsswitch.conf'
 maybe chmod 0644 './ntp.conf'
diff --git a/nilfs_cleanerd.conf b/nilfs_cleanerd.conf
deleted file mode 100644
index 13dfef8..0000000
--- a/nilfs_cleanerd.conf
+++ /dev/null
@@ -1,64 +0,0 @@
-# nilfs_cleanerd.conf - configuration file of NILFS cleaner daemon.
-#
-# This file contains GC parameters that are loaded when cleaner gets
-# started.  You can force them to be reloaded by sending a HUP signal
-# to the cleaner process.
-#
-# Each parameter is declared with a keyword-value pair or a directive
-# with no argument.  Lines beginning with "#" are ignored.  For
-# details, see the man page of nilfs_cleanerd.conf(5).
-
-# Protection period in second.
-protection_period	3600
-
-# Minimum number of clean segments
-#   0 = continuous cleaning
-# > 0 = pause cleaning until less segments are available
-min_clean_segments	10%
-
-# Maximum number of clean segments
-max_clean_segments	20%
-
-# The argument of min_clean_segments and max_clean_segments can be
-# followed by a percent sign (%) or one of the following
-# multiplicative suffixes: K 1024, MB 1000*1000, M 1024*1024, GB
-# 1000*1000*1000, G 1024*1024*1024, and so on for T, P, E.
-#
-# If the argument is followed by "%", it represents a disk capacity
-# ratio.
-
-# Clean segment check interval in seconds
-clean_check_interval	10
-
-# Segment selection policy.
-# In NILFS version 2.0.0, only the timestamp policy is supported.
-selection_policy	timestamp	# timestamp in ascend order
-
-# The maximum number of segments to be cleaned at a time.
-nsegments_per_clean	2
-
-# The maximum number of segments to be cleaned at a time
-# if clean segments < min_clean_segments
-mc_nsegments_per_clean	4
-
-# Cleaning interval in seconds.
-cleaning_interval	5
-
-# Cleaning interval in seconds
-# if clean segments < min_clean_segments
-mc_cleaning_interval	1
-
-# Retry interval in seconds.
-retry_interval		60
-
-# Refresh interval to force file system to clean up segments.
-# in seconds.
-mrefresh_interval	800
-
-# Use mmap when reading segments if supported.
-use_mmap
-
-# Log priority.
-# Supported priorities are emerg, alert, crit, err, warning, notice, info, and
-# debug.
-log_priority		info