You are not logged in. Login Now
 0-24   25-49   31-55   56-80   81-105   106-130   131-155   156-180   181-205 
 206-230   231-255   256-280   281-283       
 
Author Message
25 new of 283 responses total.
keesan
response 56 of 283: Mark Unseen   Jan 12 20:53 UTC 1999

Don't we have two leftover good modems from the dropped lines?
I dial in at 9600 and have had no connection problems (when not busy signal).
scott
response 57 of 283: Mark Unseen   Jan 12 22:55 UTC 1999

I think it will be a programming issue, like the other times.  One of the
modems loses its settings...
keesan
response 58 of 283: Mark Unseen   Jan 13 05:09 UTC 1999

I just dialed in at 9600 and connected at 2400.  761-3000.  Earlier I could
not connect until I dialed 5041, at 9600.
scott
response 59 of 283: Mark Unseen   Jan 13 16:26 UTC 1999

Might be a dirty phone line issue.

Busy signals right now; means that a lot of people are dialed in after Grex
was down for a few hours.  If any modems are still misbehaving I'll be able
to check the logs.
aruba
response 60 of 283: Mark Unseen   Jan 13 19:11 UTC 1999

I got a busy signal just now, but there are only 6 people dialed in on the
terminal server.  What's up with that?
scott
response 61 of 283: Mark Unseen   Jan 13 19:57 UTC 1999

According to the terminal server, there has been no activity on lines
3,4,5,8,9 (server ports).  Clearly I need to visit the Pumpkin and find out
the truth.
scott
response 62 of 283: Mark Unseen   Jan 13 23:49 UTC 1999

I found a number of modems stuck "on", so I reset them.  That should free up
the lines.  I'll be keeping an eye on them to see if it happens again.
aruba
response 63 of 283: Mark Unseen   Jan 14 02:32 UTC 1999

Thanks Scott.
russ
response 64 of 283: Mark Unseen   Jan 14 04:14 UTC 1999

Re #59:
>Might be a dirty phone line issue.
 
I had to hang up and re-dial tonight because I got a phone
line that was spewing simply amazing amounts of noise.
gregb
response 65 of 283: Mark Unseen   Jan 14 15:16 UTC 1999

Re. 61:  Just out of curiousity, what's on 1, 2, 6 and 7?
dpc
response 66 of 283: Mark Unseen   Jan 14 16:27 UTC 1999

The MOTD says Grex was unavailable yesterday morning 1/13.  When
I logged on during that period, the System told me "sorry..."
        I didn't know if a hacker had wiped the system or what.
The next time, could the staff please post a short message
more enlightening than "sorry..."? Thanx!
aruba
response 67 of 283: Mark Unseen   Jan 14 18:16 UTC 1999

(I would've appreciated that too.  I got mail from one new user who thought
he was being told "sorry" because he had entered the wrong password.)
steve
response 68 of 283: Mark Unseen   Jan 14 23:09 UTC 1999

   Grex was rendered senseless that morning by a vandal.  When I got up
Weds morning I found I was on Grex and what I was doing was frozen at 4:18
am.  I elected to get over to the Pumkin on my way to work although I
shouldn't have, because a crisis came up and I was working via the phone
to fix it, while getting ready to head out.

   So when I got to Grex I was busy with this other problem and had to
do things as quickly as possible.  I didn't have time to fuss with a nice
message--I wanted to create the /etc/nologin file as quickly as possible
to thwart any logins as I inspected the system.  Along that time I got yet
another page and was busy working on that on the phone while working on
Grex.

   Sometimes, things don't happen as well as they should.  Sorry.  The 
alternative of course would have been for me to skip working on Grex and
let the next available staff person stuble out into the cold and get over
there and deal with it.
aruba
response 69 of 283: Mark Unseen   Jan 14 23:45 UTC 1999

We certainly appreciate your fixing it, STeve.
mic
response 70 of 283: Mark Unseen   Jan 15 00:24 UTC 1999

Thanks STeve!!  You did more than your call.
steve
response 71 of 283: Mark Unseen   Jan 15 03:51 UTC 1999

   Thanks.  With any luck the next time I have to keep people out there
will be a reasonable message explaining why.  I do realize that "sorry"
is near Zen-like, and most people prefer error messages that less resemble
a koan.
gregb
response 72 of 283: Mark Unseen   Jan 15 14:18 UTC 1999

Re. 71:  Steve, is there a way you could set up a stock msg. that displays
under such circumstances?  That way you wouldn't have to come up with
something pithy to say every time.  Not to mention saving time.
aruba
response 73 of 283: Mark Unseen   Jan 15 15:07 UTC 1999

Something like, "Sorry, Grex is cranky right now.  Call back in a little
while."
steve
response 74 of 283: Mark Unseen   Jan 15 15:49 UTC 1999

   Sure--that is an *excellent* idea.  I can make it a csh alias, and
type that one command to create the message.  Thanks!  That solves my
problem of when critically pressed for time, and informing our users.
steve
response 75 of 283: Mark Unseen   Jan 15 16:16 UTC 1999

   If you look at the file /etc/nologin.boilerplate you'll see what
will be placed in /etc/nologin if I type 'nologin' as woot.  Feel
free to suggest different phrasing, etc.  This really is a good
idea.  Thanks Greg, for suggesting it.
keesan
response 76 of 283: Mark Unseen   Jan 15 16:38 UTC 1999

Thanks Scott and STeve.
ryeguy
response 77 of 283: Mark Unseen   Jan 15 17:35 UTC 1999

my sister is an idiot is my sister doth she be
blah
flem
response 78 of 283: Mark Unseen   Jan 15 18:05 UTC 1999

re 75:  the spelling gestapo might suggest that you substitute "explanation"
for "explaination", but other than that it looks good.
steve
response 79 of 283: Mark Unseen   Jan 15 18:20 UTC 1999

   Got it.
aruba
response 80 of 283: Mark Unseen   Jan 15 18:20 UTC 1999

And the grammar KGB might object to "the staff are working", presuming they're
based in America and not England.  But it looks good to me too.
 0-24   25-49   31-55   56-80   81-105   106-130   131-155   156-180   181-205 
 206-230   231-255   256-280   281-283       
Response Not Possible: You are Not Logged In
 

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