|
|
| Author |
Message |
| 25 new of 162 responses total. |
jazz
|
|
response 100 of 162:
| 
Aug 27 15:18 UTC 1999 |
I should say large ISPs do not want to provide peering to their smaller
neighbors, not to their neighbors at all.
|
macho
|
|
response 101 of 162:
|
Aug 30 12:42 UTC 1999 |
hi !!my name is anand.anybody wanna be my friend?
|
headdoc
|
|
response 102 of 162:
|
Aug 31 23:15 UTC 1999 |
I was just in the middle of a long e-mail when all sorts of letter strings
appeared on my screen and my cursor froze. Nothing I did could get things
going again and I lost the whole darn correspondence. What causes that and
can it be rectified?
|
other
|
|
response 103 of 162:
|
Sep 1 00:07 UTC 1999 |
did someone pick up an extension phone on your modem line?
|
mcnally
|
|
response 104 of 162:
|
Sep 1 01:45 UTC 1999 |
re #102: were you dialled in directly or telnetting in? it should
*never* happen if you're telnetting in..
|
scg
|
|
response 105 of 162:
|
Sep 1 02:17 UTC 1999 |
Unless you're dialed into wherever you're telnetting from with a terminal..
|
mcnally
|
|
response 106 of 162:
|
Sep 1 04:20 UTC 1999 |
Unless you're dialed in using PPP or some other TCP-over-dialup protocol,
etc.. I was hoping not to open that can of worms by assuming that if she
was telnetted in that there was no non-error-correcting link in the chain..
|
headdoc
|
|
response 107 of 162:
|
Sep 3 21:58 UTC 1999 |
I dialed in from home. Also, we have a separate line for the computer, so
no, no one picked up the telephone extension. Any other ideas? Could it be
a break of some kind in the telephone line outside the house? Could it have
been something originating at the Grex terminal? Could it have been something
in the Pine works? I was e-mailing through pine.
Inquiring minds want to know.\
|
mooncat
|
|
response 108 of 162:
|
Sep 3 23:31 UTC 1999 |
Hmm, I wonder if it could have been cross-talk somewhere along the line.
Every once and awhile while working in one office on campus we would
get calls for a completely different office with a totally different
number- but because of interference on the line we got their calls.
So somewhere, if wire were slightly frayed and hit each other just
right you could have gotten some 'noise' through your line.
|
rcurl
|
|
response 109 of 162:
|
Sep 4 02:13 UTC 1999 |
You could have a poor connection in a modular plug; the telephone company
might have done something; an animal might have nibbled an elevated phone
wire; lightning?; wind could have rattled a bad external connection;
something might have happened at Grex (among which are all of the above
plus staff falling off their chairs.... :)
|
headdoc
|
|
response 110 of 162:
|
Sep 5 02:11 UTC 1999 |
If I had to guess, it would be the cross talk or frayed lines. No wind or
lightening at the time, Rane. A day like today. Now Grex staff members
falling off chairs. . .I am trying to envision. Everyone seems so stable.
(a psychologists pun.)
|
tpryan
|
|
response 111 of 162:
|
Sep 8 02:39 UTC 1999 |
Just had a phunny phone connect. Ring thru on the first line,
then after second line answered, a disconnect. A quick re-dial got
me in.
|
otaking
|
|
response 112 of 162:
|
Sep 8 11:13 UTC 1999 |
Yesterday, grex said that I had a bad participation file when I entered aora.
Now it says that I have 190 brandnew items. It's as if I never read anything
in this conference at all. Is there any way to fix that?
|
remmers
|
|
response 113 of 162:
|
Sep 8 11:59 UTC 1999 |
Yes - type "fixseen" at the "Ok:" prompt (if you're using Picospan and
not Backtalk). Then, to read responses new in the last day, type
"read since -1".
This problem occurs whenever Picospan tries to update your conference
participation file at a time when the disk is full. The /a disk filled
up yesterday afternoon. My participation file got zapped too.
|
otaking
|
|
response 114 of 162:
|
Sep 8 18:19 UTC 1999 |
Thanks remmers, that seems to have fixed the problem.
|
drew
|
|
response 115 of 162:
|
Sep 8 19:51 UTC 1999 |
/a is full again.
|
don
|
|
response 116 of 162:
|
Sep 8 21:02 UTC 1999 |
Hmm.... owing to the full drive, would it be worth it to back up my
participation file (say, every time I log in or something)? Are they the .cf
files?
|
other
|
|
response 117 of 162:
|
Sep 9 02:36 UTC 1999 |
yes, but only if you back them up off grex. otherwise, you are just
contributing to the problem...
|
dpc
|
|
response 118 of 162:
|
Sep 9 14:57 UTC 1999 |
I dialed in on -3000 a few minutes ago and was peaceably reading
my mail when I was disconnected. When I logged in again, here is
what the System said:
Last login: Thu Sep 9 10:46:06 on ttyqd from 204.212.46.132
I have been *repeatedly* disconnected for the past several weeks.
This is very disconcerting. Does anyone have any idea why
this is happening? Are others having this problem?
|
dpc
|
|
response 119 of 162:
|
Sep 9 15:15 UTC 1999 |
I was just disconnected *again*! When I re-connected, I was told:
Last login: Thu Sep 9 10:55:01 on ttyu7 from 204.212.46.132
Do we have a bad modem/set of modems?
|
scott
|
|
response 120 of 162:
|
Sep 9 15:40 UTC 1999 |
I haven't had any problems in a while. Have you tried from a different
location (ie not your own phone line)?
|
jazz
|
|
response 121 of 162:
|
Sep 9 17:18 UTC 1999 |
Not strictly a system problem, but an amusing error message during the
daily queue:
...3
Sep 9 13:11 Sep 9 13:11 56880 -1 11229 203.197.98.6 LOST HEAD
...2
...1
[203.197.98.6 is a part of VSNL's broken-DNS space]
|
tpryan
|
|
response 122 of 162:
|
Sep 9 21:39 UTC 1999 |
re120: Are you sure it isn't the 9/9/99 bug?
|
russ
|
|
response 123 of 162:
|
Sep 10 00:12 UTC 1999 |
One of the modems at or below -3554 in the trunk hunt is ringing open.
|
goose
|
|
response 124 of 162:
|
Sep 10 04:11 UTC 1999 |
does this look okay?:
16 waiting, 64 remote + 3 local users; 72 max remote users; 4951 head
...2 of 17; 67 users
...2 of 17; 66 users
...2 of 16; 65 users
IT's not that I had to wait a long time to get onto Grex, but I read it
as eight less people should be waiting to get on (72 max remote - 64 remote)
|
