diff options
| author | B. Watson <yalhcru@gmail.com> | 2022-03-14 13:01:56 -0400 |
|---|---|---|
| committer | B. Watson <yalhcru@gmail.com> | 2022-03-17 12:38:14 -0400 |
| commit | ef40abd0f28da196f4478c4a157774ec588a59ae (patch) | |
| tree | db0f197193bbf9fad89e88dbb3f002ce5509ddb1 /system/uptimed | |
| parent | 3fa51127e40cf8bf91da76a1a6dd28beee81b079 (diff) | |
system/uptimed: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/uptimed')
| -rw-r--r-- | system/uptimed/README | 31 |
1 files changed, 17 insertions, 14 deletions
diff --git a/system/uptimed/README b/system/uptimed/README index dc1d782990002..21d9911a16b56 100644 --- a/system/uptimed/README +++ b/system/uptimed/README @@ -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". |