This item is for system problems.  If something on Grex isn't working 
right (line noise on a modem, weird behavior from a program, etc.), 
this is the place to announce it.  Except for security holes.  If you 
find a hole in system security, mail information about it to "staff".

188 responses total.

The usual group of immature twits is having a flood-fest in the
Summer conference.  Would some system person remove the write
permissions to that agora's directory, and bring a halt to it?
It might be worthwhile to do this to all previous agoras as well.

No. There are some important threads that continue there. There is not
good reason to automatically halt ongoing threads in any conference
just because a new one has been started. In fact, twits hanging out
there reduces their presence in the current agora.

It's possible to allow responses but disallow new items, isn't it?

I would much rather the new items got entered in Summer instead of here.  In
fact it seems like an excellent division of topics.

People problems are not system problems.  This is not a good place to
have a debate about policy.  The coop conference is the place to have
that kind of discussion.

Exactly, and we've been over this in coop already.

Fork bombs are started by people too; does that make them not system
problems?

System problem:  It took 3 minutes to get a login prompt this evening.

Access to Grex via the internet is being very erratic.  From tir.com
I can't get in at all.  From msen.com I can get in sporadically with 
bad lag, connection hangs.  Not sure what the problem is, it probably
isn't local.  

  I'm not sure what the problem is but Grex is intermittently unpingable..

I had trouble coming for both backtalk and telnet when I tried 
grex.org, but no problem with cyberspace.org.... Just thought I'd 
mention it.

Fork bombs aren't a problem.  So no, they don't qualify as either people
problems or system problems.

   Yes, Grex is having net problems tonight.  All of a sudden
things have appeared to get better (about 10:14pm).  WIth luck
this will continue...

I had to dial in twice.  Once I connected, then it waited a while and
disconnected me. 5041 worked the second time.  Half an hour ago.  

I just had to dial in twice, also.  First time it gave me a burst of garbage
& then disconnected.

tried a while ago to log on via telnet.  was not successful.

I have been telnetting, and I'm getting kicked off in the middle of looking
at the cfs (lag to death) and when I try and get back on it either takes a
million years, and then says I am so far back in queue, or it can't resolve
the IP address.  Ick.

(weird. I'm in TX and haven't had any problems logging in.)

I had a lot of disconnect problems last night.  I was dialing in and kept
getting halfway through my first email message, then kicked off.

I got kicked off in the middle of reading something about 4 times before I
gave up.  Then I came back, and so far it is okay.

Hm.  I telnet and almost never have disconnect problems.  Not much
lag problem either since the upgrade to DSL.  It'd be nice to
discover if there is some common factor for the people having
such problems.

The scoop at work today was that Verio was having problems (a fairly
normal condition for them). 

The Net connection was being pretty flaky last night.  It wouldn't have been
Verio, though, connectivity from me to Grex doesn't go through Verio.

And unreachable too ...

Just now I got frozen up in mid-composition of e-mail, could not telnet back
in four tries, but dialed in okay.

The network was way bogged down, partially due to a vandal trying to flood
another system.

I lost grex telnet connectivity around 6:30pm Tue 9/26, and backtalk couldn't
grex either.  I'm dialing in now, 12:15am Wed 9/27.

Backtalk seems to be running really slowly this morning.  It's not 
timing out, but it's taking much longer than usual.

  Lately I've been experiencing long delays between the time my telnet
  program reports connecting to Grex and the time the login prompt shows
  up, even when there's no queue..

I've noticed that delay, too.

        I've been getting that delay on the dial-up server.  This morning
I got disconnected by that thing instead of Grex proper.  Some message
about My Host don't know cyberspace.org or something like that.

Grex's named wasn't running, for some reason.

While running pine today, I got the following error message:
  ld.so: call to undefined procedure _sigpause from 0xef785528
Unsurprisingly, pine crashed. 

I have gotten this message a few times, after a long delay when I tried to
send mail.

This response has been erased.

After entering logout at the shell prompt, one gets another login
prompt. Responding exit sometimes logs out, and sometimes produces
yet another login prompt. I have not detected evident cause of sometimes
getting a second chance to login again, and sometimes not. Is there
method to the madness?

Try "stty 9600" *BEFORE* connecting to grex.

I'm telneting in. 

And?

He's telnetting in.

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