rev 4530 - kde-extras/icecream/trunk/debian

[Fathi Boudra]

Author: fboudra-guest
Date: 2006-09-19 10:25:26 +0000 (Tue, 19 Sep 2006)
New Revision: 4530

Added:
   kde-extras/icecream/trunk/debian/icecc.conf
Log:
oups forget icecc.conf

Added: kde-extras/icecream/trunk/debian/icecc.conf
===================================================================
--- kde-extras/icecream/trunk/debian/icecc.conf	                        (rev 0)
+++ kde-extras/icecream/trunk/debian/icecc.conf	2006-09-19 10:25:26 UTC (rev 4530)
@@ -0,0 +1,47 @@
+#
+# Nice level of running compilers
+#
+# ICECC_NICE_LEVEL="5"
+ICECC_NICE_LEVEL="5"
+
+#
+# icecc daemon log file
+#
+# ICECC_LOG_FILE="/var/log/iceccd.log"
+ICECC_LOG_FILE="/var/log/iceccd.log"
+
+#
+# Identification for the network the scheduler and daemon run on. 
+# You can have several distinct icecc networks in the same LAN
+# for whatever reason.
+#
+# ICECC_NETNAME=""
+ICECC_NETNAME=""
+
+# 
+# You can overwrite here the number of jobs to run in parallel. Per
+# default this depends on the number of (virtual) CPUs installed. 
+#
+# ICECC_MAX_JOBS=""
+ICECC_MAX_JOBS=""
+
+#
+# This is the directory where the icecc daemon stores the environments
+# it compiles in. In a big network this can grow quite a bit, so use some
+# path if your /tmp is small - but the user icecc has to write to it.
+# 
+# ICECC_BASEDIR="/var/cache/icecc"
+ICECC_BASEDIR="/var/cache/icecc"
+
+#
+# icecc scheduler log file
+#
+# ICECC_SCHEDULER_LOG_FILE="/var/log/icecc_scheduler.log"
+ICECC_SCHEDULER_LOG_FILE="/var/log/icecc_scheduler.log"
+
+#
+# If the daemon can't find the scheduler by broadcast (e.g. because 
+# of a firewall) you can specify it.
+#
+# ICECC_SCHEDULER_HOST=""
+ICECC_SCHEDULER_HOST=""