|
Grex > Helpers > #48: System Problems Item. Please attempt to rhyme where possible. |  |
|
| Author |
Message |
| 25 new of 231 responses total. |
blh
|
|
response 100 of 231:
| 
Oct 22 13:32 UTC 1996 |
Over the streets and by the parks
do the Dungeons house we go.
The truck knew the way,
but park there?no way!
but to make the move
we still droove.
We put parts in boxes
moved the "Steelcase" like foxes,
and found the pumpkin all reet
The fleet did the beat
and now is all neet
Thanks to our new home
on West Huron Street
|
popcorn
|
|
response 101 of 231:
|
Oct 22 21:12 UTC 1996 |
Re 98:
I've been on h4 for hours,
completely free of line-noise showers.
|
olddraco
|
|
response 102 of 231:
|
Oct 22 21:59 UTC 1996 |
I'm on H3, no noise, but....it took 7 minutes to invoke PINE and be at my
inbox, I gave up waiting for a !w olddraco does this slowness mean that
that thing for reading the confs by www is niced better than anything else?
|
popcorn
|
|
response 103 of 231:
|
Oct 23 16:21 UTC 1996 |
Nope. It means Grex is busy
enough to make one dizzy.
|
kerouac
|
|
response 104 of 231:
|
Oct 24 18:28 UTC 1996 |
what is "unknown child: 9536" I have been getting this error in
picospan lately.
|
scg
|
|
response 105 of 231:
|
Oct 25 05:27 UTC 1996 |
Richard, it means you're about to be hit with a paternity suit. ;)
Grex was down all afternoon and evening, apparrently because the disk
with /home on it overheated. Marcus cleaned and oiled the fans, and we made
a backup in case anything else goes wrong. Everything seems to be working
fine now.
|
giry
|
|
response 106 of 231:
|
Oct 25 06:21 UTC 1996 |
<It is too late for me to rhyme, sorry.>
I was just put on the que, and there were only 23 users. When I was
at #3 I got this message: Oct 25 02:04 Oct 25 02:04 185 -1 5390 144.16.68.173
LOST HEAD
I have no clue what it means, but I thought it might be important.
|
cmcgee
|
|
response 107 of 231:
|
Oct 25 08:04 UTC 1996 |
When I tried to get my mail
Picospan me did fail.
This response I did get
Mail program to use? pine
^\/usr/local/bin/menu: 15431 Quit
* M A I N M E N U *
When our Grex had its snit.
Second time around was good,
My simple "pine" was understood.
|
ajax
|
|
response 108 of 231:
|
Oct 25 11:26 UTC 1996 |
When pressing return, at a "Respond or pass?"
The following errors appeared en masse:
> Respond or pass?
> WARNING: terminal cannot clear to end of line
> WARNING: terminal cannot clear screen
> WARNING: terminal cannot home cursor
> WARNING: terminal cannot move cursor to lower left of screen
> WARNING: terminal cannot scroll backwards
>
> - (press RETURN)
I've changed not a thing, and never before
have I seen this strange behavior
|
bjorn
|
|
response 109 of 231:
|
Oct 25 14:59 UTC 1996 |
I saw that behavoir plenty of times when I was telnetting to Grex from Winona
State U's Vax system.
|
kerouac
|
|
response 110 of 231:
|
Oct 25 15:16 UTC 1996 |
well you know the more older and well worn an program gets ,, the
more likely it gets to throw out weird error messages...picospan
cant be blamed if its bones creak once in a while.
|
popcorn
|
|
response 111 of 231:
|
Oct 25 15:33 UTC 1996 |
Re 106: Marcus needs to know about that.
Re 108: Rob, that's the symptom people see when their termcap isn't set right,
especially if they've got type "dumb". It's why I want to get us a better
newbie pager -- the conferences are awfully hard to use with those messages
popping up everywhere.
Sorry about the lack of rhyme.
Right this minute, it takes too much time.
|
srw
|
|
response 112 of 231:
|
Oct 26 01:25 UTC 1996 |
Telnetd monitors its queue,
The oldest becomes the head.
if a younger one (you)
thinks that the head is dead,
it complains about the LOST HEAD.
So that is a queue self-correcting diagnostic. It shouldn't be seen often,
and probably ought to be reported, but it is not critical.
|
ajax
|
|
response 113 of 231:
|
Oct 31 00:50 UTC 1996 |
Many an error,
It's quite a terror!
|
davel
|
|
response 114 of 231:
|
Oct 31 14:06 UTC 1996 |
Grex was down a long time!
(Hey, this time I can even rhyme!)
|
blh
|
|
response 115 of 231:
|
Oct 31 15:52 UTC 1996 |
having grex back
is a great fack
|
wolfg676
|
|
response 116 of 231:
|
Oct 31 21:40 UTC 1996 |
Having Grex back is really fine,
Although I do spend too much time on-line.
Suffering through deep depression
from being unable to open a telnet session,
I found myself starting to whine.
And now that it's back,
My e-mail is stacked,
and downloading it will take too much time.
<eep! 580K! eep!>
BTW, what is a "fack"?
|
blh
|
|
response 117 of 231:
|
Nov 1 00:22 UTC 1996 |
well,,, it is not a lack!
|
bjorn
|
|
response 118 of 231:
|
Nov 1 02:01 UTC 1996 |
A lot of times when I change station,
Grex doth retort
"terminated: segmentation"
|
ajax
|
|
response 119 of 231:
|
Nov 1 09:00 UTC 1996 |
That plague I've had a long duration
So long it gives no excitation!
|
albaugh
|
|
response 120 of 231:
|
Nov 1 18:16 UTC 1996 |
Grex performance yesterday (10/31) around 5pm was so bad that I had to
disconnect my telnet session, after waiting ~5 minutes for mail to finally
come up but only display a couple of lines then pause "indefinitely".
Before that, around 3pm, I encountered the following:
Waiting for a free port (? for help)
...9
...8
...7
...6
Warning, continued inactivity will cause session to be terminated.
Idle timeout exceeded, session terminated.
Connection closed by foreign host.
Seems like while you're in the queue, you wouldn't be expected to be doing
any regular typing, would you? :-)
|
janc
|
|
response 121 of 231:
|
Nov 1 18:44 UTC 1996 |
I can't see how idled would be hitting people who don't have a pty yet.
A "fack" is a FAQ or a "Frequently asked question" list.
Various people think Grex's CPU board is ill. We'll probably try swapping
in our spare sometime soon.
|
tsty
|
|
response 122 of 231:
|
Nov 2 10:29 UTC 1996 |
albaugh ..
when waiting for an open line
send a ? ing time
the answer will give you extra stuff
to use to keep your foreign host
a happy grex and local host from timing out
|
albaugh
|
|
response 123 of 231:
|
Nov 3 10:27 UTC 1996 |
Yeah, sure, I could "babysit" my waiting for port connection with a stray
entry now & then. But that doesn't make sense to have to do that. And just
to clarify, it was grex that timed out and closed the connection, not the
host I was telnetting from...
|
drew
|
|
response 124 of 231:
|
Nov 3 20:10 UTC 1996 |
That often happens to me, too; and I have discovered that it is usually
lag. Grex has done its job and sent you the prompt, it is just having a
hard time getting through the network. I have lately tried entering my
password no more than 15 seconds or so after I hit the carriage return for
my username, whether I have a Password: prompt or not. The last couple of
times I tried this, I managed to get onto grex.
|