Subj : Re: Network Monitoring
To   : Brian Rogers
From : Wilfred van Velzen
Date : Thu May 27 2021 05:54 pm

Hi Brian,

On 2021-05-27 09:26:00, you wrote to me:

 WvV>> I wasn't asking how to do it, I was asking what the difference was
 WvV>> between the two methods. In my opinion both methods can give you the
 WvV>> same information, so you don't need to do a separate ping to know if
 WvV>> a system is online or not.

 BR> I did show what the difference was. One method could easily be done via a
 BR> script. The other would intail more indepth coding.

Looking at your outbound, only needs a set of eyes and fingers, no other tools 
required! ;)

 WvV>> Again: You don't need to ping, just look at what's in your
 WvV>> outbound... ;)

 BR> Wrong my friend. A point who doesn't desire to have crash mail that may
 BR> poll once a week would show mail stuck in the outbound and read a very
 BR> false positive.

Such a point won't be pingable either. So you also need information about your 
links, that was implied, and would be something a sysop looking at his outbound 
would know.

 BR> Now my question is: for what purpose would such a thing serve?
 BR> Entertainment value?? That's all I can really see this for.

It serves the smooth operation of the network.

 BR> If the goal is to see if a node or point left an FTN that's one thing
 BR> and monitoring one's outbound should be more than sufficient, and in
 BR> reality such a tool should be included in the FTN mailers to auto mail
 BR> the sysop "mail for #:###/### has been in your queue for 30 or more
 BR> days." Again in the interim this could probably be handled by a shell
 BR> script that can be cronned that mails the sysadmim/sysop.

Such a tool would make the sysops live a bit easier, but you don't really need 
it. You don't need to automate it, the commands provided by your OS (cd/dir/ls) 
are sufficient to find out if your outbound is full of unsend mail.

 BR> Other than that I don't see where someone in 3:###/### for example
 BR> would need or want to see my boring stats.

I didn't know we were talking about making this information public?

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)

.