said Sharon Kimble via tde-users:
| Why use a script, does your linux setup have a program called 'uptimes' | (in Debian) which uses the command `uprecords` which gives your longest | uptimes and your cumulative uptimes and your cumulative downtimes.
I have "uptime," which renders a one-line summary of how long the computer has been on, the load, etc., but is silent on connections. I have no "uprecords" or "uprecord." I've looked at a variety of tools. Apparently "gping" is no longer maintained; the Gnome tools don't log and don't allow anything except the Linux ping default, which is once per second. I looked at, installed, and tried unsuccessfully to configure "Smokeping," which is like bringing in a battle tank to get rid of a wasp nest. I had hoped that there would be some lightweight utility that would include what I wanted, which is a record of the times my ISP fails to PIS, as proof of their unreliability, chapter and verse. It seems to have turned out that a script does this when nothing else does.
(It performed during one of the failures earlier today.)
I've thrown it and the log in a little ~/ subdirectory, stuck an icon on it and put it in Kmenu. So one click and it is running, and I can always monitor it by looking at the terminal that's generated. In that it generated more than a megabyte of log per day, I'd like to cook up a way to automate archiving of the existing log, with date, daily. As it is, I can just move the file into an archive subdirectory and rename it at whatever frequency, probably weekly, I'd like. Then, when it's needed, it will be simple to provide a list of times it's been down, to within three seconds.
| Does this help?
It's good to know -- I was unaware of the utility -- but in this case it doesn't do what I need.
Thanks.