|
|
| Author |
Message |
| 25 new of 187 responses total. |
mcnally
|
|
response 32 of 187:
| 
Apr 8 21:57 UTC 1997 |
Probably you temporarily exhausted the supply of zerros left in the
/dev/zero queue.. :-)
Actualy, probably either a messed up /dev file or a shared lib problem.
|
dpc
|
|
response 33 of 187:
|
Apr 9 19:25 UTC 1997 |
I'm getting the "chopped-up responses" problem again. I am on ttyh3.
I *think* this is the same modem that was doing this a couple months
ago.
|
tsty
|
|
response 34 of 187:
|
Apr 11 05:04 UTC 1997 |
naughty-naughty mcnally .................... tsk
|
dpc
|
|
response 35 of 187:
|
Apr 27 22:54 UTC 1997 |
Around 2:00 this afternoon I *tried* to log on. Well, actually,
I dialed 761-3000, some modem connected, I saw part of the MOTD,
and then Grex hung up on me!
|
valerie
|
|
response 36 of 187:
|
Apr 28 01:08 UTC 1997 |
This response has been erased.
|
lee
|
|
response 37 of 187:
|
Apr 28 01:11 UTC 1997 |
Hi. I typed pine and got the normal pine screen for a moment. Then it
printed out "Floating exception" and kicked me back out and gave me a UNIX
prompt. I tried again, same thing happened. Any ideas?
|
kaplan
|
|
response 38 of 187:
|
Apr 28 01:29 UTC 1997 |
Use oldpine instead of pine. The version of pine on grex was replaced
recently in case anyone doesn't know.
|
davel
|
|
response 39 of 187:
|
Apr 28 10:46 UTC 1997 |
Re 36: I *think* he meant that he saw part of the MOTD without logging in,
if I'm reading it right. Sounds like some lag in hanging up?
|
valerie
|
|
response 40 of 187:
|
Apr 28 11:34 UTC 1997 |
This response has been erased.
|
rcurl
|
|
response 41 of 187:
|
May 3 19:35 UTC 1997 |
Uh...was there a fire?
"Broadcast Message from scg@grex.cyberspace.org (console) at 15:13 ...
Going off the Internet now. We should be back in about 15 minutes."
No warning...just disconnected. Its one thing if its an emergency; another
if it was just thoughtless.
|
scg
|
|
response 42 of 187:
|
May 3 19:40 UTC 1997 |
I did send a warning a few minutes before that. Did you not get it?
No fire; just a little hardware work on Gryps I had said I would do about six
weeks ago. Gryps needed to be turned off for a minute to do that.
|
rcurl
|
|
response 43 of 187:
|
May 3 20:08 UTC 1997 |
No, I didn't get the warning, though it's possible I got it in pine while
I was doing something that would have cleared it simultaneously with it
being presented (sometimes when pine seems to hang, I do a ^L to see if it
is still awake, and that would clear such a message). How about a couple
of warnings 5, 10 and 15 minutes prior? I've sort of gotten used to that
protocol from other staff.
|
valerie
|
|
response 44 of 187:
|
May 5 03:50 UTC 1997 |
This response has been erased.
|
rcurl
|
|
response 45 of 187:
|
May 5 04:30 UTC 1997 |
Then it wasn't working that time.
|
scg
|
|
response 46 of 187:
|
May 5 04:33 UTC 1997 |
I wasn't shutting Grex down. I just shutdown gryps, the Internet router, and
only for a few minutes. The effect people would have noticed would have been
the same as if the net link had gone down briefly, or gryps crashed, which
happens a couple of times a day.
|
rcurl
|
|
response 47 of 187:
|
May 5 16:29 UTC 1997 |
Well...more notice would still be welcome, if possible. We live with the
inevitable but can control the intentional.
|
tao
|
|
response 48 of 187:
|
May 5 18:02 UTC 1997 |
The shutdown command will give several warnings, if specified.
shutdown -h <time> <message>
where <time> can be x minutes from now, at hh:mm, or now,
and <message> = "something to inform users about service interuption"
if time is +60, shutdown will halt the system in 60 minutes, with
periodic notices bradcast to all logins. As shutdown time approaches,
these broadcasts increase in frequency.
|
dpc
|
|
response 49 of 187:
|
May 6 23:26 UTC 1997 |
Is "shutdown" permitted to staff only?
|
arianna
|
|
response 50 of 187:
|
May 6 23:38 UTC 1997 |
I would imagine...
|
senna
|
|
response 51 of 187:
|
May 7 00:20 UTC 1997 |
Yeah, it's only accessible with a root password that only staff members
know... and some programs are only accessible to select staff members
|
dang
|
|
response 52 of 187:
|
May 7 00:57 UTC 1997 |
Yeah, shutdown is root only.
|
kentn
|
|
response 53 of 187:
|
May 7 05:41 UTC 1997 |
...and a good thing, too.
(do shutdown messages from gryps show up on grex?)
|
scg
|
|
response 54 of 187:
|
May 7 05:51 UTC 1997 |
No, shutdown messages from gryps show up only on gryps.
|
albaugh
|
|
response 55 of 187:
|
May 7 18:09 UTC 1997 |
Is "gryps" the machine that manages grex's sessions? Is there a
one-to-one correspondence in sessions between gryps & grex? Or does
gryps merely manage the internet connection, and grex handle its own
connections (I don't see how...) ? Anyway, assuming that gryps is also
a Unix machine, does *its* shutdown warn the grex users running through
it?
|
dang
|
|
response 56 of 187:
|
May 7 18:41 UTC 1997 |
Gryps is a unix machine, called a router, and it handles Grex's internet
connection. The link modem is attached to gryps, and it runs ppp over that
modem to IC Net. All incoming traffic to gryps is forwarded to Grex (Unless
that traffic is specifically for gryps) and grex handles all of the
connections. So, you do not have a session with gryps when you are here. As
a matter of fact, no one but staff even has login's on gryps. The shutdown
messages on gryps are only on gryps, and so you would not see them here. All
that would happen is that your telnet session would freeze, and, of gryps was
down long enough, it would time out. If gryps isn't down long enough, then
it just freezes for a while, and then starts back up.
|
