blob: 21d9911a16b565530df48608994ecbd4dd09bd66 (
about) (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
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>:<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.
If performing an upgrade, you may need to chmod 755 rc.uptimed and
restart the daemon with "/etc/rc.d/rc.uptimed restart".
|
