|
|
| Author |
Message |
i
|
|
Grex System Problems Item
| 
Dec 22 04:56 UTC 1998 |
This item is for system problems. If something on Grex isn't working
right (line noise on a modem, weird behavior from a program, etc.),
this is the place to announce it. Except for security holes. If you
find a hole in system security, mail information about it to "staff".
|
| 283 responses total. |
hhsrat
|
|
response 1 of 283:
|
Dec 24 19:42 UTC 1998 |
I have noticed that I see a different MOTD when I log in via backtalk
than what I see when I login via telnet.
|
toking
|
|
response 2 of 283:
|
Dec 24 20:11 UTC 1998 |
huh? the formatting is a little off in backtalk...but i never noticed
different content...
|
hhsrat
|
|
response 3 of 283:
|
Dec 25 02:05 UTC 1998 |
there are some messages in the telnet version (like the ICNET message)
that aren't in the BT version
|
senna
|
|
response 4 of 283:
|
Dec 25 10:58 UTC 1998 |
Once again, the net connection is dead. What's been happening with it? This
is becoming awfully frequent.
|
steve
|
|
response 5 of 283:
|
Dec 25 19:21 UTC 1998 |
It was down from about 5:22a to 9:37a today. I believe that things
are being tested; Christmas morning is one of those prime times to test
things out.
I wouldn't say they're awfully frequent, just noticeable enough that
we can remember them from one outage to another. Given the donation of
the ISDN link, I'm willing to accept these occaisonal outages as a part
of the package. Most of them have been at off-peak times for us local
folks.
|
rcurl
|
|
response 6 of 283:
|
Dec 26 01:43 UTC 1998 |
I am unable to connect via compuserve. I get a login prompt, but that is
quickly dropped with a message that the connection was closed by the host.
I am now connected via a double telnet via Michnet.
|
janc
|
|
response 7 of 283:
|
Dec 28 17:40 UTC 1998 |
Re resp:3:
Grex actually has three MOTD files - the one with the ICNET message,
the one with the birthday announcments, and the one with everything
else. I think Backtalk doesn't do the ICNET one, which is kind of
OK, since we no longer use ICNET's connection. Other than this, and
formatting, they should always be the same.
|
steve
|
|
response 8 of 283:
|
Dec 29 16:04 UTC 1998 |
Grex ran out of space on the "/a" partition at 3:54am today. An
idiot was FTPing an entire OS here (beos) but ran out of Grex before
it ran out of beos to FTP. Removed it.
|
keesan
|
|
response 9 of 283:
|
Dec 29 17:06 UTC 1998 |
STeve, when do you sleep?
|
steve
|
|
response 10 of 283:
|
Dec 29 17:43 UTC 1998 |
At those various off times when 1) kids 2) work 3) grex allows it.
|
jared
|
|
response 11 of 283:
|
Dec 30 03:22 UTC 1998 |
that should have been
when {kids, work, grex} allows it
|
steve
|
|
response 12 of 283:
|
Dec 30 03:36 UTC 1998 |
Hey, the kids encourage grex work--or they can't get on maybe.
|
aruba
|
|
response 13 of 283:
|
Jan 4 18:18 UTC 1999 |
I've been unable to dial in for the last couple of hours; the modem connects,
but then I don't get any text. I'm telnetted in now.
|
keesan
|
|
response 14 of 283:
|
Jan 4 18:21 UTC 1999 |
I just dialed in okay, shortly before you telnetted in.
|
scott
|
|
response 15 of 283:
|
Jan 4 20:36 UTC 1999 |
There is apparently one evil modem that is doing that "connect but no message"
bit.
|
gregb
|
|
response 16 of 283:
|
Jan 4 20:45 UTC 1999 |
Request to all: To help keep track of what response goes with which
msg., please try to remember to put the original msg. # in your
response. Some of these confs. have a rapid turnover, which means it's
possible to come into a conf and read msgs. that have no apparent
meaning, unless you know which msg. was the origin.
Those that are already doing this, it's appreciated.
|
rcurl
|
|
response 17 of 283:
|
Jan 4 21:32 UTC 1999 |
(This announcement is getting as bad as that $24,000 for $6 thing...:) )
|
keesan
|
|
response 18 of 283:
|
Jan 5 02:31 UTC 1999 |
At least it was well meant. I always read confs from the beginning and have
not found it a problem to figure out what was being referred to.
|
jared
|
|
response 19 of 283:
|
Jan 5 02:57 UTC 1999 |
put "b n" in your .cfrc
|
i
|
|
response 20 of 283:
|
Jan 5 04:08 UTC 1999 |
Got busy signals ~1 hour ago. Then could only get through on a too-noisy-
to-use line. (Dialed elsewhere & telnetted some, so probably not my stuff
or line.) I'm in on a good dial-in now.
|
gregb
|
|
response 21 of 283:
|
Jan 6 15:06 UTC 1999 |
Re. 17: Since not everybody reads all confs., this seemed like the logical
course of action. If you have a viable alternative that accomplishes the same
thing, let me know.
|
remmers
|
|
response 22 of 283:
|
Jan 6 17:45 UTC 1999 |
(But that doesn't explain why you put it in multiple items in the *same*
conference.)
|
gregb
|
|
response 23 of 283:
|
Jan 8 14:39 UTC 1999 |
Re. 22: Wrong wording on my part. I should have said "item," though my
previous statement still applies.
|
keesan
|
|
response 24 of 283:
|
Jan 8 20:15 UTC 1999 |
I think just about everyone reads the first couple of items.
|
