summaryrefslogtreecommitdiff
path: root/system/uptimed/README
diff options
context:
space:
mode:
authorGraham Orange <gorange40@gmail.com>2014-04-11 01:18:22 +0700
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2014-04-11 01:24:12 +0700
commitd4e8c61fafba3b438ef7a19403305b09e8d0f6eb (patch)
tree04c7c49e501c82640c636a391c756b3f82ae6fa8 /system/uptimed/README
parent96c3b4238ea54b45be6f47b3628372f929235854 (diff)
downloadslackbuilds-d4e8c61fafba3b438ef7a19403305b09e8d0f6eb.tar.gz
system/uptimed: Added (An uptime daemon).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'system/uptimed/README')
-rw-r--r--system/uptimed/README35
1 files changed, 35 insertions, 0 deletions
diff --git a/system/uptimed/README b/system/uptimed/README
new file mode 100644
index 0000000000..e96a9c0bdb
--- /dev/null
+++ b/system/uptimed/README
@@ -0,0 +1,35 @@
+uptimed (An uptime deamon to log your best uptimes)
+
+Stores your best uptime statistics in "/var/spool/uptimed/records"
+
+The 'uprecords' command will display your best uptime results.
+
+Note: See below on how to launch uptimed automatically.
+Additional configuration via "/etc/uptimed.conf"
+ (See "/etc/uptimed.conf-dist")
+
+The uptimed daemon runs in the background and regularly stores the following
+data to "/var/spool/uptimed/records";
+"<Uptime in seconds>:<Boot up in unixtime>:<System kernel name and release>"
+The boot up value is used as a unique identifier.
+
+See "uprecords -?" for additional record display options.
+
+The "uprecords" file can be copied as "uprecords.cgi" to your CGI directory,
+and will render Content-type head information and HTML tabs as necessary.
+(See "INSTALL.cgi" in the extracted source for more information.)
+
+To have the daemon launch automatically at boot time,
+ 1) Set the rc.uptimed file as executable;
+ chmod 755 /etc/rc.d/rc.uptimed
+ 2) Add an entry in rc.local with;
+ if [ -x /etc/rc.d/rc.uptimed ]; then
+ /etc/rc.d/rc.uptimed start
+ fi
+
+Q: Why are my records not saved between reboots? I can see the current uptime
+ info with the 'uprecords' command.
+A: The uptimed daemon was possibly not running to regularly save the data to the
+ "/var/spool/uptimed/records" file. See above on how to automatically start
+ the daemon, and confirm that the "/var/spool/uptimed" directory exists
+ and is writable.