From: fbrehm Date: Mon, 12 Mar 2012 15:58:28 +0000 (+0100) Subject: committing changes in /etc after emerge run X-Git-Url: https://git.uhu-banane.de/?a=commitdiff_plain;h=fac1e02c65d7490cca25f188980140e5e68e7450;p=config%2Fsamara%2Fetc.git committing changes in /etc after emerge run Package changes: +sys-fs/nilfs-utils-2.1.0 --- diff --git a/.etckeeper b/.etckeeper index 9528025..42df851 100755 --- a/.etckeeper +++ b/.etckeeper @@ -1171,6 +1171,7 @@ 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 new file mode 100644 index 0000000..26872aa --- /dev/null +++ b/nilfs_cleanerd.conf @@ -0,0 +1,60 @@ +# 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 + +# 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