You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   134-158   159-183   184-208 
 209-233   234-251         
 
Author Message
25 new of 251 responses total.
gelinas
response 159 of 251: Mark Unseen   Feb 4 03:41 UTC 2003

Probably at the very end of the line, as in the lines just before it.

In general, quotation marks come in pairs.
carson
response 160 of 251: Mark Unseen   Feb 4 12:20 UTC 2003

(ttyp0 appears to still be stuck in wtmp.)

  7:04am  up 33 days, 21:03,  44 users,  load average: 11.46, 12.04, 12.16
User     tty       login@  idle   JCPU   PCPU  what
carson   ttyp0     7:04am            9      3  w 
mullen   ttyp0     1:51am            9      3  w 

remmers
response 161 of 251: Mark Unseen   Feb 4 13:48 UTC 2003

Re #159:  Picospan is forgiving about a missing close-quote at the end
of a line.
keesan
response 162 of 251: Mark Unseen   Feb 4 17:26 UTC 2003

I will refrain from fixing what works even if it is not perfect.  I am afraid
of causing more problems by adding back the quotation mark.
aruba
response 163 of 251: Mark Unseen   Feb 4 20:39 UTC 2003

I believe -t makes pico exit and save when you hit ^X, whereas without it
you get those two annoying prompts asking if you *really* want to save and
if you *really* want to exit.
davel
response 164 of 251: Mark Unseen   Feb 5 14:14 UTC 2003

That's right.  Except s/annoying/outrageously annoying & confusing/
krokus
response 165 of 251: Mark Unseen   Feb 7 15:45 UTC 2003

When connecting with ssh, the screen clears itself after motd, doesn't
display the Last login or mail status, and starts the cleared screen
with the Erase info.
mynxcat
response 166 of 251: Mark Unseen   Feb 7 15:56 UTC 2003

This response has been erased.

goose
response 167 of 251: Mark Unseen   Feb 7 16:05 UTC 2003

It still happens when I use PuTTY.
gull
response 168 of 251: Mark Unseen   Feb 7 16:36 UTC 2003

That happens to me with TeraTerm, regardless of how I connect.  I think
Grex sends a terminal reset command right before doing the Erase stuff.

I have .hushlogin set anyway, because I prefer to diff the motd so I
only have to read the changes, not the whole thing every time.
krokus
response 169 of 251: Mark Unseen   Feb 8 15:12 UTC 2003

I'm using putty for my ssh sessions, and NetTerm for telnet sessions.
I have no prolbems when using NetTerm.  I guess I'll have to see how
I can get Grex to stop sending a reset, if that's what it's doing.
krokus
response 170 of 251: Mark Unseen   Feb 9 22:29 UTC 2003

The whole systems seems to be having issues, or is at least losing
most/all connections.
mcnally
response 171 of 251: Mark Unseen   Feb 9 22:34 UTC 2003

My ssh connection has been dropped several times today, ditto for telnet.
Generally within a few minutes of my connecting, the session will seem to
freeze, with characters I type evidently not reaching whatever program I'm
in at the time.  About a minute or so later my ssh client (putty) gives up
the ghost and declares the connection terminated.

If I ping grex from a command prompt window while my putty session is
frozen, packets seem to be getting through at least as far as grex.org.
Is anyone else experiencing this or should I be looking for explanations
on my end first?
gull
response 172 of 251: Mark Unseen   Feb 9 22:37 UTC 2003

ssh and web access has been very erratic for me today.  I'm dialed in right
now, but earlier that wasn't working, either.
cmcgee
response 173 of 251: Mark Unseen   Feb 9 22:41 UTC 2003

I've had problems with telnet and ssh in the past couple hours.
keesan
response 174 of 251: Mark Unseen   Feb 9 23:01 UTC 2003

I could not dial or telnet in just now.  Using backtalk (6 pm).
jmsaul
response 175 of 251: Mark Unseen   Feb 9 23:12 UTC 2003

I'm in via SSH right now.
keesan
response 176 of 251: Mark Unseen   Feb 9 23:18 UTC 2003

Now I was able to telnet (17 min after my first five attempts).
aruba
response 177 of 251: Mark Unseen   Feb 9 23:43 UTC 2003

I got dumped earlier today too.
gelinas
response 178 of 251: Mark Unseen   Feb 10 00:16 UTC 2003

Generally, I use traceroute when I notice problems like those described
above, and, generally, I see that packets are being dropped between
voyager and grex.  Here is an excerpt from the results of a such test
from right now:

} 10  rback0.flnt.mi.voyager.net (216.93.15.210)  56 ms  51 ms  51 ms
} 11  cyberspacecomm.flnt.mi.voyager.net (216.93.107.238)  113 ms  63 ms  65 ms
} 12  grex.cyberspace.org (216.93.104.34)  65 ms  59 ms  67 ms

It's right after hop 10 I see trouble.

Earlier today, I noticed such things, when I was logged in (via ssh)
between 14:56 and 15:38.  I guess my ssh client was more tolerant,
because I did not lose my connection.
davel
response 179 of 251: Mark Unseen   Feb 10 02:06 UTC 2003

Earlier, I was dialed in & telnetted out (Grex is the only ISP I've got),
and kept getting hung up (um, frozen, not disconnected - if I pressed ^]
I got immediate response from telnet).  A bit later, Jon was on (dialed in)
and kept getting disconnected.  The fact that dialins were disconnected
at that point suggests something local to Grex, but possibly in the
network connection to the termserver.
jhudson
response 180 of 251: Mark Unseen   Feb 10 20:27 UTC 2003

I'm getting something similar now.
Telnet connections need 1 minute to login prompt.
Backtalk slogs rather badly too.
Normal (non-cgi) HTTP is fine.
keesan
response 181 of 251: Mark Unseen   Feb 22 16:27 UTC 2003

Pine keeps dumping me when I try to send a mail (several times a week):
ld.so call to undefined procedure _sigpause from 0xef785528
russ
response 182 of 251: Mark Unseen   Feb 24 00:10 UTC 2003

Grex took over 140 seconds to give a login prompt.
gelinas
response 183 of 251: Mark Unseen   Feb 24 00:47 UTC 2003

DNS for grex.org isn't working.  Both dns.gibbard and grex.cyberspace
fail:

        res_send to server dns.gibbard.org  209.142.209.52: Connection
                refused

and

        res_send to server grex.cyberspace.org  216.93.104.34: Connection
                timed out
 0-24   25-49   50-74   75-99   100-124   125-149   134-158   159-183   184-208 
 209-233   234-251         
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss