| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | not all is lost but far too much for far too long |
On 2019 Jul 04 23:24:38, you wrote to me: ml>> the mechanism is the *Cs MK> So I brought this up in the wrong echo? i dunno... it was easier where there was an IC... MK> This seems like the place for thes issues. the FTSC was the proper place and it would pass the word to the IC who then sent down the notice to the ZCs who sent it to the RCs who sent it to the NCs who contacted the nodes with the problematic software... ml>> i don't have a clue what you're speaking of MK> I was just responding to the line that says, "getting that mechanism into MK> operation like used to be done is a little harder to do these days for some MK> reason". It sounded like a "back in the good ol' days" type of thing. MK> Sorry if I read that wrong. oh... the lack of an IC has hampered numerous things in fidonet... sure the ZCC looks to be able to do the same tasks but getting edicts handed down might be troublesome... ml>> we have to find exactly which software it is causing it MK> Good idea. the hard part will be getting hold of those operators and getting them to backlevel until a fix is out... some of them set their systems up and they run unattended except for maybe once a month or so when the operator decides to look in on it... by then they could be out of the nodelist and not even know it since a lot of the newer software doesn't even require a nodelist to operate... i seem to be tagging at least one or two operators a week who's systems have gone TITSUP (Total Inability To Support Usual Performance) for several days... when my outbound is approaching 2000+ PKTs for one system, i start to get real antsy... i can see it pretty easily since i have a bash script that monitors my BSO and checks the flo files' contents for a count and date/time of the oldest file listed... )\/(ark And to this end they built themselves a stupendous super-computer which was so amazingly intelligent that even before its data banks had been connected up it had started from "I think therefore I am" and got as far as deducing the existence of rice pudding and income tax before anyone managed to turn it off. ... Press to test. Release to detonate... ---* Origin: (1:3634/12.73) SEEN-BY: 1/120 14/6 18/0 103/705 123/0 25 50 115 150 755 135/300 153/7001 7715 SEEN-BY: 154/10 30 40 700 203/0 221/0 6 227/201 400 229/310 426 240/5832 SEEN-BY: 261/38 280/464 5003 5006 5555 292/854 310/31 320/219 340/800 396/45 SEEN-BY: 423/120 633/267 280 640/1384 712/620 848 770/1 2452/250 3634/0 12 15 SEEN-BY: 3634/24 27 50 119 5020/545 @PATH: 3634/12 154/10 280/464 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.