 |
 |
 |
1.) [Linu x] rc_pingr [start|stop|restart]
This tool is for monitoring when a host becomes unaccessible. It's handled with a common rc-handler. Which also makes it autostart at a reboot. The output uses the virtual terminal 4 to list what's happening and also saves to a log. To reduce the needed bandwith the ping intervall begins at 3 min and increases gradually to 19 min. When stopping the intervall wishes to finish before action is taken so even here, don't work in a hurry. If your ravaging forces you to cleanup up afterwards, maybe you should have taken that time in the first place. Besides the usual commands, there are some additional ones:
* -h Print the usage screen, selfexplanatory, I hope.
* isuph Ping multi hosts visually, explained below.
* isupv Ping multi hosts listing, explained below.
* -r List the log of what's happened so far, hopefully very short.
2.) [Li nux] rc_pingr isuph
This tool will, at a glance, show the status of the computers on the LAN. It shows a line indicating which boxes are on or off.
oXoXXo
3.) [Linux] rc_pingr isupv
Here's a tool that will list the host name and the status. Can be used to spell out which box is the unconnected one.
1 192.168.0.2 [ OK ]
2 192.168.0.3 [ Down ]
3 midgard [ OK ]
4 Danella [ Down ]
Both above programs, isup(h|v), works with a common host file. And I know there's no builtin support of colors in version 0.2.7 so I borrowed the colorization module from version 0.3.x, without remorse.
The log option lists what's in the log:
031022-15:02 pingr started: 192.168.1.24
031025-22:15 down: 192.168.1.24
031025-22:49 up: 192.168.1.24
-----
031028-19:38 pingr halted: 192.168.1.24
To make an installation on your Freesco box, a keyboard and a monitor must be connected and your privileges have to be root.
Start from the point where this is assumed to begin.
[Lin ux] cd
Ready to get some pingers aboard? Off we go.
[ Linux] installpkg http://www.abc.se/%7Em989/Frsco/pkgs/pingr_0.14_ysby-027
It is kind of working by itself. At the beginning there's a question whether you want to proceed. Well, make your decision.
Now, enter the user configurable data.
[ Linux] edit /mnt/router/packages/pingr/isup.hsts
A file with hosts to be supervised in the format:
[ IP-nbr/URL-name | space | descriptive-name ]
192.168.0.5 Danella
Two parts on the line separated by space. Comments are allowed and must begin with a "#", octothorpe for the initiated, character. And no empty lines, please. The descriptive name shall have a length of 1 to 15 chars, inclusive. Not limiting the descriptive name to max 15 chars will create misalignment of the output list. If you can live with that, well, be my guest.
[Linu x] edit /mnt/router/packages/pingr/pingr
You'll supply the IP and a name of the box.
* TNOD IP address to check as dot quad nbr.
* TNME Human readable name.
[Linu x] edit /mnt/router/packages/pingr/smtpc
If you want to be notified by mail you have to supply some information,
* SMTPSRV Your ISP SMTP server.
* SENDR A valid domain name.
* RECPT Receiver of the message, you?
* SUBJCT Subject, to differentiate from all other mail.
* MSG Default message.
Time to start, and you don't have to reboot, of course.
[Li nux] rc_pingr start
With the previous steps done without any missteps, it starts pinging.
Typing "ps" shows the pinger.
[Linux] ps
598 S 1 pingr sh./pingr
If you need a finer granularity when things happens to the node you're surveying, there is another client supplied. Copy it to the general name, edit and restart.
[Li nux] cd /mnt/router/packages/pingr
[ Linux] cp percon pingr
[Linux] edit pingr
[Linux] cd
[Linux] rc_pingr restart
And off you go. This client is designed to have some hysteresis to be smooth when the connection bounces. You don't feel better with a magnitude more messages? You have users in one end on your lan, they'll tell you, right?
Jalla! Jalla!