You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-248          
 
Author Message
25 new of 248 responses total.
davel
response 125 of 248: Mark Unseen   Nov 5 14:47 UTC 2002

(So was I.)
albaugh
response 126 of 248: Mark Unseen   Nov 7 19:56 UTC 2002

I have to confirm that I, too, am seeing long delays in e-mail delivery to
grex, something I didn't used to see.  There may not have been anyone
consciously done by anyone, but something could have changed in the
environment...
russ
response 127 of 248: Mark Unseen   Nov 9 00:15 UTC 2002

The modem on -3596 is very noisy.  Is there any chance of
replacing it with the one formerly on -2517 and seeing if
matters improve?
scott
response 128 of 248: Mark Unseen   Nov 9 04:02 UTC 2002

Trouble is I don't know which modem was on 2517.  :(
tpryan
response 129 of 248: Mark Unseen   Nov 9 21:04 UTC 2002

        Take a cell phone to the pumpkin.  Dial the number.
Notice with one answers.
scott
response 130 of 248: Mark Unseen   Nov 10 00:31 UTC 2002

"was".
russ
response 131 of 248: Mark Unseen   Nov 15 12:35 UTC 2002

Mail from at least one system to Grex is being
dropped silently.
keesan
response 132 of 248: Mark Unseen   Nov 15 14:50 UTC 2002

Mail is still arriving late - took more than 12 hours - so perhaps yours is
still on the way.  One person wrote me that three of his mails to me bounced
due to the connection to grex timing out.
keesan
response 133 of 248: Mark Unseen   Nov 15 17:12 UTC 2002

The person whose mail arrived late said she had tried several times yesterday
to email and it kept bouncing.  She finally phoned my answering machine.
She does not get these bounce messages when mailing other places.  
THis makes it sort of a problem to use email at grex for business purposes.
Right now email is working fine.
polytarp
response 134 of 248: Mark Unseen   Nov 17 02:04 UTC 2002

Picospan will not accept my full title.  As Autocrat of all Russias, I deserve,
expect, and demand better.

Fix it, or I will be upset.
janc
response 135 of 248: Mark Unseen   Nov 17 14:37 UTC 2002

I doubt it.
remmers
response 136 of 248: Mark Unseen   Nov 17 15:24 UTC 2002

I move that a name length limit of 48 characters be implemented.
keesan
response 137 of 248: Mark Unseen   Nov 17 16:17 UTC 2002

Or a way to wrap lines in names so that they don't split mid-word.
slynne
response 138 of 248: Mark Unseen   Nov 17 21:35 UTC 2002

Names wrap well in backtalk. 
janc
response 139 of 248: Mark Unseen   Nov 17 21:54 UTC 2002

Aside from ugly wrappinng, Picospan seems to have no problem displaying long
names.
other
response 140 of 248: Mark Unseen   Nov 17 22:32 UTC 2002

uh huh.
davel
response 141 of 248: Mark Unseen   Nov 18 01:00 UTC 2002

AFAICS, Picospan doesn't wrap long names at all.  The wrap is imposed by the
terminal emulation used by the user.
remmers
response 142 of 248: Mark Unseen   Nov 18 02:00 UTC 2002

Are we having fun yet?
jmsaul
response 143 of 248: Mark Unseen   Nov 18 02:05 UTC 2002

They can't?  What do you do in the perennial hypothetical case where someone
posts a credit card number?
other
response 144 of 248: Mark Unseen   Nov 18 02:08 UTC 2002

uh huh
jmsaul
response 145 of 248: Mark Unseen   Nov 18 02:32 UTC 2002

Heh...
janc
response 146 of 248: Mark Unseen   Nov 18 04:56 UTC 2002

In that perennial hypothetical case, cfadm or root edits the response. 
Incidentally, they can edit the pseudonym too.
davel
response 147 of 248: Mark Unseen   Nov 18 13:12 UTC 2002



Re 142: I guess we must be, John.  Why else is this continuing?



jhudson
response 148 of 248: Mark Unseen   Nov 19 18:18 UTC 2002

lol
fuzzman
response 149 of 248: Mark Unseen   Nov 20 17:28 UTC 2002

wierdness:

fuzzman@cyberspace.org's password: 
Warning: Remote host failed or refused to allocate a pseudo tty.
Warning: no access to tty (Bad file number).
Thus no job control in this shell.
mesg: I/O stream 2 improperly redirected
stty: TCGETS: Operation not supported on socket
stty: standard input: Operation not supported on socket
TERM: Undefined variable.
stty: standard input: Operation not supported on socket
mesg: I/O stream 2 improperly redirected

Is someone hogging ttys?
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-248          
Response Not Possible: You are Not Logged In
 

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