Thanks for all the suggestions. I view the report on Firefox already, and it is horribly slow and almost always pops up a "script on this page is not responding" message. If I have to send an email from the station then I already know it is running.
2011/01/20 18:47 N8GFO-10 144.970 1200 EMCOMM CN84IO 2.1.0.4 Current
The leading time and date, and trailing status are the two things I want to watch. I can pipe this data to a script that will notify my if there is a problem.
The only advantage for a specific query link (like adding a "stationcall=N8GFO-10" parameter to the existing PacketStatus link) would be to reduce the load on the server.
I've found the answer. http://www.winlink.org/dotnet/status/PacketStatus.aspx produces a "printer friendly" page that contains the status info I need and I can grep out the stations I want to know about. E.g.:
lynx -dump -nolist -width=120 http://www.winlink.org/dotnet/status/PacketStatus.aspx | grep N8GFO
And I get:
2011/01/20 18:47 N8GFO-10 144.970 1200 EMCOMM CN84IO 2.1.0.4 Current
The leading time and date, and trailing status are the two things I want to watch. I can pipe this data to a script that will notify my if there is a problem.
The only advantage for a specific query link (like adding a "stationcall=N8GFO-10" parameter to the existing PacketStatus link) would be to reduce the load on the server.
Thanks.