Ward Dossche wrote to Fernando Toledo <=-
There's also substantial khrap in the ZONE4-segment, for example
...
;A Region 90: http://www.momiabbs.com.ar (Spanish)
I think there is no "http://www.momiabbs.com.ar" at all.
Plus ...
;S Zone Mail Hour
;S --------------
;S
;S Zone 5 mail hour (01:00 - 02:00 UTC)
;S Zone 2 mail hour (02:30 - 03:30 UTC)
;S Zone 4 mail hour (08:00 - 09:00 UTC)
;S Zone 1 mail hour (09:00 - 10:00 UTC)
;S Zone 3 mail hour (17:00 - 18:00 UTC)
;S Zone 6 mail hour (20:00 - 21:00 UTC)
* Zone-5 was removed 12 years ago from the nodelist
* Zone-6 was removed 17 years ago from the nodelist
I stopped being bothered by it because it seems impossible to get
anything changed/corrected in Z4 for decades.
Don't the sysops have a sense of pride or achievement to get
things done properly?
El 18/2/24 a las 23:38, Dan Clough escribi贸:You touch it, you own it. Congratulations ;)
WD> Don't the sysops have a sense of pride or achievement to get
WD> things done properly?
Apparently they don't.
I suggest you start by firing the asshole, and put somebody in there
that wants to actually do the job.
Things *can* be cleaned up.
I am going to investigate how to apply as a ZC
thanks!
--- SBBSecho 3.20-Linux
* Origin: Dock Sud BBS - https://bbs.docksud.com.ar (4:902/26)
WD> Don't the sysops have a sense of pride or achievement to get
WD> things done properly?
Apparently they don't.
I suggest you start by firing the asshole, and put somebody in there
that wants to actually do the job.
Things *can* be cleaned up.
I am going to investigate how to apply as a ZC
The job needs to be vacant, then you need an election by the RCs.
Basically the current ZC has to un-elect himself. Talk to Manuel, I think he is pretty decent and open to the idea ... with only 3 RCs in the region it could be managed quick ... well, that is if John Dovey in Panama is still breathing.
The job needs to be vacant, then you need an election by the RCs.
Basically the current ZC has to un-elect himself.
If that fails there is the last resort of the impeachment
procedure documented in P4 8.7.
I know about that but it has never been done and, my opinion, it's not
a good time to start doing that now.
The IC has a role in in, but it is the RCs that must initiate it.
That may be a bit of a challenge with only one out of four RCs being
reachable...
It also makes an election easy...
I am going to investigate how to apply as a ZC
Ward Dossche wrote to Dan Clough <=-
I suggest you start by firing the asshole, and put somebody in there
that wants to actually do the job.
Somebody with a distinct law degree and a beautiful little
daughter is not exactly an asshole.
The zones are autonomous in selecting their ZC ... P4 is clear
about that. The IC cannot do anything about it ...
Alas.
Ward Dossche wrote to Michiel van der Vlist <=-
If that fails there is the last resort of the impeachment procedure documented in P4 8.7.
I know about that but it has never been done and, my opinion,
it's not a good time to start doing that now.
If a person at any level above sysop is unable to properly perform
their duties, the person at the next level may replace them. For
example, if a Regional Coordinator fails to perform, the Zone
Coordinator can replace him.
Does that not imply that the ZCC (and/or the IC) cannot replace a ZC? Seems like it does, to me. Perhaps worth a discussion amongst the
ZCC.
4:80/0 fido.rbt.net.br:24554 35.192.92.175 Ok.
4:80/1 fido.rbt.net.br:24554 35.192.92.175 Error: Socket read error.
4:80/0 fido.rbt.net.br:24554 35.192.92.175 Ok.
4:80/1 fido.rbt.net.br:24554 35.192.92.175 Error: Socket read error.
:-m
Hello Fernando,
On Monday February 19 2024 01:06, you wrote to Dan Clough:
FT> I am going to investigate how to apply as a ZC
4:902/26 bbs.docksud.com.ar:24554 2803:9800:a015:831e:523e:aaff:fe0f:fb01 Ok.
I see you are back on IPv6. Great! I will put you back on the list.
Nodelist for Monday, February 19, 2024 -- Day number 050 parsed, 29 IP-nodes processed (0.009 sec)
4:4/0 momiabbs.no-ip.info:24554 181.229.121.152 Error: Connection timed out 4:80/0 fido.rbt.net.br:24554 35.192.92.175 Ok.
4:80/1 fido.rbt.net.br:24554 35.192.92.175 Error: Socket read error.
4:88/0 mastodontbbs.hopto.org:24554 181.162.198.58 Error: Connection timed out
4:90/0 momiabbs.no-ip.info:24554 181.229.121.152 Error: Connection timed out 4:90/1 momiabbs.no-ip.info:24554 181.229.121.152 Error: Connection timed out 4:92/0 gatofuego.synchronetbbs.org:24554 104.200.24.109 Error: Connection timed out
4:92/1 gatofuego.synchronetbbs.org:24554 104.200.24.109 Error: Connection timed out
4:801/0 fido.rbt.net.br:24554 35.192.92.175 Ok.
4:801/10 softsolutions.net.br:24554 177.23.233.122 Ok.
4:801/189 bsbbs.com.br:24554 179.180.145.169 Error: Connection timed out 4:801/197 bbs.rclabs.com.br:24554 85.208.48.115 Ok.
4:801/200 rmsbbs.ddns.net:24554 179.190.142.218 Ok.
4:801/202 baffa.zapto.org:24554 187.79.81.18 Ok.
4:880/0 mastodontbbs.hopto.org:24554 181.162.198.58 Error: Connection timed out
4:880/1 mastodontbbs.hopto.org:24554 181.162.198.58 Error: Connection timed out
4:900/0 momiabbs.no-ip.info:24554 181.229.121.152 Error: Connection timed out 4:900/100 momiabbs.no-ip.info:24554 181.229.121.152 Error: Connection timed out
4:900/102 thevaultbbs.ddns.net:24554 190.111.203.94 Ok.
4:900/107 darkgame.buanzo.org:24554 31.193.168.246 Error: Connection refused 4:900/108 zooropabbs.ddns.net:24554 181.45.26.197 Error: Connection timed out 4:902/0 momiabbs.no-ip.info:24554 181.229.121.152 Error: Connection timed out 4:902/7 reisub.nsupdate.info:24554 181.12.214.46 Ok.
4:902/19 ferchobbs.ddns.net:24554 181.23.124.217 Error: Connection timed out
4:902/26 bbs.docksud.com.ar:24554 2803:9800:a015:831e:523e:aaff:fe0f:fb01 Ok.
4:902/26 bbs.docksud.com.ar:24554 186.123.101.23 Ok.
4:902/27 momiabbs.no-ip.info:24554 181.229.121.152 Error: Connection timed out
4:902/100 momiabbs.no-ip.info:24554 181.229.121.152 Error: Connection timed out
4:920/0 gatofuego.synchronetbbs.org:24554 104.200.24.109 Error: Connection timed out
4:920/1 gatofuego.synchronetbbs.org:24554 104.200.24.109 Error: Connection timed out
So John Dovey is currently not connectable.
Of course this is just one moment in time, it might change in the future hours/days...
Btw: I count 4 RC's. Of which only 1 is connectable right now...
So John Dovey is currently not connectable.
Of course this is just one moment in time, it might change in the future
hours/days...
Btw: I count 4 RC's. Of which only 1 is connectable right now...
this is not good =(
4:88/0 mastodontbbs.hopto.org:24554 181.162.215.135 Error: Connection timed out16,17c16,17
4:880/0 mastodontbbs.hopto.org:24554 181.162.215.135 Error: Connection timed out22c22
4:880/1 mastodontbbs.hopto.org:24554 181.162.215.135 Error: Connection timed out
4:900/108 zooropabbs.ddns.net:24554 52.4.41.44 Error: Connection timed out24c24
4:902/7 reisub.nsupdate.info:24554 181.91.5.227 Ok.
Ward Dossche wrote to Dan Clough <=-
If a person at any level above sysop is unable to properly perform their duties, the person at the next level may replace them. For example, if a Regional Coordinator fails to perform, the Zone Coordinator can replace him.
It doesn't work in the case of the ZC if the RCs don't follow ...
an IC is a toothless tiger if the ZCC does not operate as 'one'.
Does that not imply that the ZCC (and/or the IC) cannot replace a ZC? Seems like it does, to me. Perhaps worth a discussion amongst the ZCC.
Talk to whom there? Nick will respond but other than that there's
a lot of echo.
Don't give up hope, yet.
I can tell you about not giving up hope against all odds ...
Ward Dossche wrote to Dan Clough <=-
It's hard to imagine a scenario where there could be a better time.
Let me try it another way, suppose as IC I would decide to
replace ZC1 just like that.
How successful do you think I would be?
The IC is a toothless tiger ... that has been demonstrated in the
past.
this is not good =(
I did another test today. Some IP numbers changed, but not the connection test results.
Ward Dossche wrote to Flavio Bessa <=-
I think that John has shut down his system... He is now travelling
over South Africa and his BBS seem to be down.
Well, then obviously his presence in the nodelist, of lack
there-of, needs to be managed one way or the other ... Failing
that Z4 will contain inactive regions with closed-down nodes and
a ZC not dealing with it.
Even in the closed ZCC-echo among ZCs the ZC4 is absent. Last
sign of life Jan 22 2022. But I see Manuel on and of on Facebook.
Ward DosPkt message 1 屯 ZCC-PUBLIC WD> I know about that but it has never been done and, my opinion,WD> it's not a good time to start doing that now.
It's hard to imagine a scenario where there could be a better time.
I mean, the ZC and 3 of the 4 RC's are not connectable? Why isn't that
a "good time to start"? It needs to be done.
Ward Dossche wrote to Dan Clough <=-
DC> It's hard to imagine a scenario where there could be a better time.
WD> Let me try it another way, suppose as IC I would decide to
WD> replace ZC1 just like that.
That would be a whole 'nother situation, and that replacement would not
be justified. The difference here, of course, is that the ZC in
question has disappeared and is un-reachable. Seems like reasonable
time and effort has been dispensed in *TRYING* to reach him. At what
point does that unacceptable behavior (and Zone status) become something
that needs decisive action to correct? Is it allowed to go on
indefinitely? Seems stupid to allow that, as it clearly is not good for
the health of FidoNet.
WD> How successful do you think I would be?
Not very, for reasons discussed just above. There's no defend-able
reason to replace that ZC, but there is for the other.
WD> The IC is a toothless tiger ... that has been demonstrated in the
WD> past.
There's an old saying that I've heard (and used a few times): Sometimes
it's better to ask forgiveness than to seek permission. I don't see how anyone in FidoNet would think this (replacing the AWOL ZC) is not a
justified and necessary action. It's for the betterment of FidoNet.
Fernando Toledo wrote to Dan Clough <=-
El 22/2/24 a las 00:08, Dan Clough escribi贸:
Ward Dossche wrote to Dan Clough <=-
DC> It's hard to imagine a scenario where there could be a better time.
WD> Let me try it another way, suppose as IC I would decide to
WD> replace ZC1 just like that.
That would be a whole 'nother situation, and that replacement would not
be justified. The difference here, of course, is that the ZC in
question has disappeared and is un-reachable. Seems like reasonable
time and effort has been dispensed in *TRYING* to reach him. At what
point does that unacceptable behavior (and Zone status) become something that needs decisive action to correct? Is it allowed to go on
indefinitely? Seems stupid to allow that, as it clearly is not good for
the health of FidoNet.
Exactly, this is not a power dispute... we are just a few crazy
nodes. It's a technical issue, I want the things to work.
And when they don't work, they can be made to work and not expect
that one person, because they are busy with other matters, will
leave the entire area adrift.
WD> How successful do you think I would be?
Not very, for reasons discussed just above. There's no defend-able
reason to replace that ZC, but there is for the other.
WD> The IC is a toothless tiger ... that has been demonstrated in the
WD> past.
There's an old saying that I've heard (and used a few times): Sometimes it's better to ask forgiveness than to seek permission. I don't see how anyone in FidoNet would think this (replacing the AWOL ZC) is not a justified and necessary action. It's for the betterment of FidoNet.
It is not necessary for the IC to change to the ZC, but rather
the ZC must come clean and step aside, leaving others to continue
holding the zone while he cannot do so.
4:88/0 mastodontbbs.hopto.org:24554 181.162.198.58 Error:
Connection timed out
Can you please retest 4:88/0? System is back online now.
On 19 Feb 2024, Wilfred van Velzen said the following...
Wv> 4:88/0 mastodontbbs.hopto.org:24554 181.162.198.58 Error: Connection
Wv> timed out
Can you please retest 4:88/0? System is back online now.
Wv> 4:88/0 mastodontbbs.hopto.org:24554 181.162.198.58 Error:I see it offline.
Connection
Wv> timed out
Can you please retest 4:88/0? System is back online now.
| Sysop: | Fercho |
|---|---|
| Lugar: | La Plata, Buenos Aires |
| Usuarios: | 33 |
| Nodos: | 10 (0 / 10) |
| Uptime: | 01:36:37 |
| Llamadas: | 119 |
| Archivoss: | 15,607 |
| Mensajes: | 32,786 |