|
|
| Author |
Message |
| 25 new of 248 responses total. |
spankie
|
|
response 36 of 248:
| 
Oct 5 14:21 UTC 2002 |
oh ya it's grexwalk day. i'll go smoke a joint then, goverdomme.
|
spankie
|
|
response 37 of 248:
|
Oct 5 14:23 UTC 2002 |
"
Logins are currently denied by /etc/nologin:
Connection to cyberspace.org closed.
"
|
scott
|
|
response 38 of 248:
|
Oct 5 14:28 UTC 2002 |
Grex was down due to power problems. I just now removed the login block.
|
jmsaul
|
|
response 39 of 248:
|
Oct 5 14:40 UTC 2002 |
Re #35: Yeah. Look us up when you're in Chicago.
|
spankie
|
|
response 40 of 248:
|
Oct 5 15:00 UTC 2002 |
actually it's a bit dodgy as i'm arriving at maybe 8ish and am expecting a
ride who's coming from st louis, which ain't that close last i checked, so
i may be there over night and i apologize in advance for the toilet paper
beady may or may not find squushed to his windows. drink and pool anyone?
pardon the digression./
|
keesan
|
|
response 41 of 248:
|
Oct 5 15:47 UTC 2002 |
Thanks Scott!
|
russ
|
|
response 42 of 248:
|
Oct 5 17:53 UTC 2002 |
Earlier today, Grex was accepting id and password, then hanging
up without so much as a by-your-leave.
Damned rude of it.
I was calling 2517, but that shouldn't have made a difference.
|
aruba
|
|
response 43 of 248:
|
Oct 5 23:44 UTC 2002 |
Russ:Not that this is your problem, but - 761-2517 is the line that I told
Ameritech to drop yesterday, so if it hasn't gone away yet, it should be
going away very soon.
|
scott
|
|
response 44 of 248:
|
Oct 6 02:08 UTC 2002 |
It was probably the nologin after the reboot doing that to Russ - the terminal
doesn't stay open long enough to see the message. I didn't have time to stick
around and babysit the reboot, so it took an hour or two to remove the
nologin.
|
russ
|
|
response 45 of 248:
|
Oct 6 12:53 UTC 2002 |
Logged in today to find 102 spams in my mailbox, with probable
loss of real mail due to blockage.
Someday these idiots are going to get their comeuppance.
|
happyboy
|
|
response 46 of 248:
|
Oct 6 18:16 UTC 2002 |
oooH! are you gonne dress up like spock and give them
the "Vulcan Death Grope"?
|
vargy
|
|
response 47 of 248:
|
Oct 6 20:40 UTC 2002 |
hello
|
happyboy
|
|
response 48 of 248:
|
Oct 6 20:41 UTC 2002 |
hallo, kemosabe.
|
other
|
|
response 49 of 248:
|
Oct 6 23:14 UTC 2002 |
Barking Spider....
|
polytarp
|
|
response 50 of 248:
|
Oct 7 00:35 UTC 2002 |
I was just mail-bobmed by user "mfucker"! Could someone check it out?!
|
russ
|
|
response 51 of 248:
|
Oct 7 02:05 UTC 2002 |
If the message from nologin is often swallowed by the disconnect
sequence before it has a chance to get out the modem, can staff
put a reasonable delay (such as 5 seconds) before the disconnect
so the user has a chance to actually see it?
There's not much point in issuing a message if it can't get to
the intended recipient.
|
gull
|
|
response 52 of 248:
|
Oct 7 02:21 UTC 2002 |
I think the problem is people setting their terminal software on 'close
window on disconnect' mode.
|
tpryan
|
|
response 53 of 248:
|
Oct 7 05:42 UTC 2002 |
Does that mean we now have a good modem to replace the
suspect one on on the advertised number?
|
mcnally
|
|
response 54 of 248:
|
Oct 7 22:24 UTC 2002 |
About 20 minutes ago I was bbsing when my bbs session suddenly stopped.
The word "Terminated" appeared on my terminal and I was dumped back into
my shell, which continued responding for about 15 seconds before it, too,
was abruptly terminated (or so I presume, because my terminal window
closed.)
I logged back in and uptime looks normal:
6:23pm up 2 days, 8:58, 42 users, load average: 4.30, 3.36, 2.83
So did some root person decide to send SIGTERMs to my processes (no biggie)
or do we have something odd going on?
|
other
|
|
response 55 of 248:
|
Oct 7 22:50 UTC 2002 |
Dial-in or telnet?
|
mcnally
|
|
response 56 of 248:
|
Oct 8 00:01 UTC 2002 |
telnet.
|
mcnally
|
|
response 57 of 248:
|
Oct 8 00:01 UTC 2002 |
well, strictly speaking not telnet but ssh..
|
russ
|
|
response 58 of 248:
|
Oct 8 00:08 UTC 2002 |
Trying to send a telegram to a long-idle user, the tel program froze
and could not be terminated with either the break signal, the quit
signal, or the suspend signal. I had to hang up.
This is very unfriendly behavior from a program. (The freeze was
before the message prompt was issued, so I'm assuming that it
occurred when tel tried to open the other user's tty.)
|
keesan
|
|
response 59 of 248:
|
Oct 8 01:46 UTC 2002 |
Twice while in Pine I was unable to continue typing, nor could I exit Kermit
or even reboot. Is grex responsible or might it be my computer misbehaving?
(Can problems at grex while online crash my computer so it won't reboot? I
know other things can crash it that way.) 7615041
|
gull
|
|
response 60 of 248:
|
Oct 8 01:54 UTC 2002 |
What's described in #54 has happened to me, too, on occasion.
|
