perfsonar development work

Author: dfn.calim
Date: 2014-03-10 11:44:20 +0000 (Mon, 10 Mar 2014)
New Revision: 860

Added:
   trunk/perfsonar-oppd/build/debian/scripts/perfsonar-oppd.default
Log:
adding debian default script

Copied: trunk/perfsonar-oppd/build/debian/scripts/perfsonar-oppd.default 
(from rev 825, trunk/contrib/debian/oppd.default)
===================================================================
--- trunk/perfsonar-oppd/build/debian/scripts/perfsonar-oppd.default          
                  (rev 0)
+++ trunk/perfsonar-oppd/build/debian/scripts/perfsonar-oppd.default    
2014-03-10 11:44:20 UTC (rev 860)
@@ -0,0 +1,40 @@
+# Path to oppd.
+#DAEMON=/usr/bin/oppd.pl
+
+# Configuration file to be used by oppd.
+#CONFFILE=/etc/oppd.conf
+
+# pid file to use. The init script overwrites the pid file used (from
+# configuration file or default) to make sure that the init script can 
control
+# the daemon via the pid file. Therefore you can change the pid file ONLY 
here!
+#PIDFILE=/var/run/oppd.pid
+
+# log file to use. If you set a log file here, it will not only be set as the
+# log file used by the daemon (overriding value from configuration file). The
+# daemon will also care about the ownership of the file based on the 
variables
+# DAEMONUSER and DAEMONGROUP you can find below.
+#LOGFILE=""
+
+# User to run the daemon as. Files (especially the pid file and log file, see
+# above) created by the daemon will be owned by this user.
+#DAEMONUSER=perfsonar
+
+# Group id used for pid file and log file (see above).
+#DAEMONGROUP=perfsonar
+
+# Additional command line arguments (overriding options from configuration
+# file!).
+#DAEMON_ARGS=""
+
+# Time to wait for the daemon to die, in seconds. If this value is set too 
low
+# you might not let the daemon die gracefully and 'restart' may not work.
+#DIETIME=30
+
+# Time to wait for the daemon to start, in seconds. If this value is set each
+# time the daemon is started (on start or restart) the script will stall to 
try
+# to determine if it is running. If it is not set and the server takes time
+# to setup a pid file the log message might be a false positive (says it did
+# not start when it actually did)
+# Example: STARTTIME=2
+#STARTTIME=""
+