Miroirs/slackbuilds_ponce
1
0
Fork 0
mirror of https://github.com/Ponce/slackbuilds synced 2024-11-29 13:00:32 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

system/uptimed: Wrap README at 72 columns.

Browse source 
Signed-off-by: B. Watson <yalhcru@gmail.com>
This commit is contained in:
B. Watson 2022-03-14 13:01:56 -04:00
parent 3fa51127e4
commit ef40abd0f2
1 changed files with 17 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
system/uptimed/README
View file

@ -8,16 +8,19 @@ 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 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.)
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;
@ -27,12 +30,12 @@ To have the daemon launch automatically at boot time,
/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.
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".
If performing an upgrade, you may need to chmod 755 rc.uptimed and
restart the daemon with "/etc/rc.d/rc.uptimed restart".