The temporary lines are so overwhelmed, currently, with people trying to get into the server, that NO ONE is able to function on FurryMuck (SM) at this time.
I find this odd because FurryMUCK seems to have zero trouble getting as far as quickly sending the initial (pre-connect command) page. In the 1/3 of the time things go beyond that, everything seems nice and zippy until *thud* no more connection, not "slow".
It looks identical to a case I saw where someone made the mistake of turning on Explicit Congestion Notification in the 2.4.x Linux kernel when they recompiled the kernel, without bothering to check the warning in the config process, where it notes this does not work with many routers and firewalls yet. Though I've seen the same with an *extremely* overwhelmed and underpowered router.
I'm assuming of course that kernel limits on the number of connections, et cetra aren't in effect or have been turned off in /proc and PAM's config files.
The temporary lines are so overwhelmed, currently, with people trying to get into the server, that NO ONE is able to function on FurryMuck (SM) at this time.
I find this odd because FurryMUCK seems to have zero trouble getting as far as quickly sending the initial (pre-connect command) page. In the 1/3 of the time things go beyond that, everything seems nice and zippy until *thud* no more connection, not "slow".
It looks identical to a case I saw where someone made the mistake of turning on Explicit Congestion Notification in the 2.4.x Linux kernel when they recompiled the kernel, without bothering to check the warning in the config process, where it notes this does not work with many routers and firewalls yet. Though I've seen the same with an *extremely* overwhelmed and underpowered router.
I'm assuming of course that kernel limits on the number of connections, et cetra aren't in effect or have been turned off in /proc and PAM's config files.