|
|
Well, m-net doesn't seem to be responding. From the messages that I got on the remote system logger, it looks like someone has set off another fork bomb. Preventing this from happening again will be the first priority when m-net comes back up. I'm guessing this may not be until after the first of the year, though. We should also look into a way of doing a remove cold reboot. have a happy new year!
21 responses total.
What's a fork bomb? Is that what that kid did that damaged the hardware so badly it had to be replaced at a cost of $3,000? ;-)
nevermind, it's back :)
I thought freebsd had some sort of anti-forkbomb logic built in? Fork bombs have definitely become a non-issue on grex since we took steps to build an effective defense against them.
Probably something that has to be enabled, and was overlooked...
M-net is refusing telnet connections.
This response has been erased.
Connection attempts to m-net are timing out.
There's a problem with the password file, and Rex and Tony are working on it. More details as they're available, but some people may be able to get on now.
ah, that explains why my ID doesn't exist.
It's back up now.
[Universe starts breathing again.]
down!
waaaaa
Temporary down to do a system update. No biggie. Back up by 5.
move along... nothing to see here. wimmin just get so panicky during 'that time of the month'.
Down until 11pm.
But one can read bbs via webyapp! :)
How'd we go from 5 pm to 11 pm?
I know that the system after the upgrade suddenly wanted to fsck the drives. I don't know why it is now 11pm though. Last I heard from Rex, he was on his way to Livonia to fsck the drives. He must have found more issues.
"due to complications in system upgrade, m-net will be down until 11pm."
-- rex
At this point I don't think we have an estimate. Currently the upgrade is failing on stuff that should be working. We're working on it.
Response not possible - You must register and login before posting.
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss