|
|
| Author |
Message |
| 25 new of 274 responses total. |
nephi
|
|
response 75 of 274:
| 
Jan 10 04:06 UTC 1997 |
LOL!!!
|
valerie
|
|
response 76 of 274:
|
Jan 10 07:21 UTC 1997 |
This response has been erased.
|
ryan1
|
|
response 77 of 274:
|
Jan 10 18:07 UTC 1997 |
--Another problem:
The `locate` command is broken. It works once in a while, but most of
the time it gives me a segmentation fault. Was it recently re-compiled?
It used to work perfectly.
|
srw
|
|
response 78 of 274:
|
Jan 10 18:36 UTC 1997 |
locate is known to be broken. It began failing more than a month ago. It
is a mystery as to why. It is on the list of things for some staffer to
look into. No one is going after it at the moment.
|
valerie
|
|
response 79 of 274:
|
Jan 10 18:45 UTC 1997 |
This response has been erased.
|
dpc
|
|
response 80 of 274:
|
Jan 10 21:15 UTC 1997 |
Nope, I've changed absolutely *nothing,* which is why the problem is
so disturbing.
|
remmers
|
|
response 81 of 274:
|
Jan 11 11:41 UTC 1997 |
I doubt that it's a Picospan problem. The symptoms suggest
a flow control problem between your modem and Grex's. Do
you have the problem on some sessions but not others? And what
phone number do you dial? Grex has two kinds of modems -- fast
error-correcting ones and slow 2400 baud dumber ones. If the
data loss occures during certain sessions but not others, it
might be because the communications at your end is set up
correctly for one type of modem but not the other.
|
dpc
|
|
response 82 of 274:
|
Jan 11 17:19 UTC 1997 |
I *believe* the problem was due to one Grex modem. It has only
occurred during one session; everything is fine now. FWIW, during
that same session flow control using ctrl-q and ctrl-s was slow.
Normally it is instantaneous. I hope this helps track down the
modem.
I have a dim memory that I was coming in on h3. This
may not be right.
|
valerie
|
|
response 83 of 274:
|
Jan 11 18:49 UTC 1997 |
This response has been erased.
|
wolfg676
|
|
response 84 of 274:
|
Jan 13 08:19 UTC 1997 |
Grex seems to have crashed (sort of). None of the dialins are working,
so I'm using Backtalk to post this from M-Net. Did just the modems go
down?
|
ajax
|
|
response 85 of 274:
|
Jan 13 09:28 UTC 1997 |
Not sure even the dial-ins are all down - two users are dialed in,
one since before your post. Telnet usage is fine - even a queue
to get on. How many and which phone numbers did you try?
|
robh
|
|
response 86 of 274:
|
Jan 13 11:10 UTC 1997 |
Yep, I was dialed in before that response was entered, and
I haven't had any problems. I'll make sure the modems are all
answering.
|
dang
|
|
response 87 of 274:
|
Jan 13 15:00 UTC 1997 |
At some time last night, I got open ringing on the modems. I assumed Grex
was stuck, and went on about my other business.
|
e4808mc
|
|
response 88 of 274:
|
Jan 13 18:13 UTC 1997 |
I tried to dial in twice on Sunday, and got open ringing for more than an hour
each time. It was searching, though. (I could hear the burp after three
rings as it switched to the next modem).
|
valerie
|
|
response 89 of 274:
|
Jan 13 18:48 UTC 1997 |
This response has been erased.
|
robh
|
|
response 90 of 274:
|
Jan 13 18:51 UTC 1997 |
To clarify, Grex crashed at around quarter to 9 PM, and was down
until I rebooted it at 1 AM. So any calls made in that interval
couldn't have connected to Grex, no matter what.
|
valerie
|
|
response 91 of 274:
|
Jan 13 19:07 UTC 1997 |
This response has been erased.
|
richard
|
|
response 92 of 274:
|
Jan 13 21:17 UTC 1997 |
What?! You mean grex was down awaiting a reboot for FOUR whole hours and not
one
staffer noticed.?! Where were you guys, all at the movies that night?! *he*
You'd think that by now a staffer would know *psychically* whenever Grex is
down
Like it should be intuition by now! *hehe*
|
richard
|
|
response 93 of 274:
|
Jan 13 21:41 UTC 1997 |
And besides, wouldnt a supersophisiticated piece of technology like grex
be able to learn to reboot itself with the right programming? Why should
grex require human intervention for a reboot! :)
|
scott
|
|
response 94 of 274:
|
Jan 13 22:24 UTC 1997 |
Hey, it's just a dumb computer.
|
dam
|
|
response 95 of 274:
|
Jan 13 22:28 UTC 1997 |
re#93: sure, but then you wouldn't know why it had crashed.
|
scott
|
|
response 96 of 274:
|
Jan 13 22:35 UTC 1997 |
Actually, the Sun3 was set up this way near the end of its life. It would
spontaneously restart itself, and staff eventually set it up to go thru all
the routine startup stuff on its own.
Trouble was, there was something like a 1% chance that with it all automated,
it might totally destroy all the disk contents when starting up.
|
janc
|
|
response 97 of 274:
|
Jan 14 03:30 UTC 1997 |
Actually, I think Grex is set up to autoreboot. Problem is, it isn't really
crashing. It's just stopping.
|
scg
|
|
response 98 of 274:
|
Jan 14 05:25 UTC 1997 |
Right. No matter what we set it to do, it wouldnt' do it if it crashed before
getting to it.
I did notice that Grex was down last night, but it was *cold* out, andI just
couldn't motivate myself to go outside in the cold and reboot it. That's
something we have to live with wiht a volunteer staff.
|
ajax
|
|
response 99 of 274:
|
Jan 14 06:31 UTC 1997 |
But just think how warm the Pumpkin is when you get there...Grex is
like a fireplace without the need for firewood! (But not quite as
comforting as fireplaces when it snaps, crackles, and pops).
Auto-restarts could theoretically be handled even when it hangs by
using an X10 controller. There are heavy duty X10 modules that would
be suitable. However, that wouldn't be an easy procedure to implement.
|
