response 26 of 68:

Oct 23 13:35 UTC 2003

As I'm not all that knowledgable about the fine points of ssh,
please explain what "uselogin yes" is.  Am I reading correctly
that it's a configuration option that, among other things, would
cause the same info to be displayed to the user on login that 
would be displayed with a telnet login?

response 28 of 68:

Oct 23 17:29 UTC 2003

But does this have the effect I asked about?

response 30 of 68:

Oct 25 15:10 UTC 2003

        I thought grex had more lines?  What is with the busy signals
on -3000?
        Where was the announcement here about the dial-in lines
being disconnected?
        Does any staff care anymore about the trunk hunt not working?
Again, an item 3 or 4 response would be nice if it is the process 
of being fixed.

response 32 of 68:

Oct 25 15:54 UTC 2003

Sorry, TIm, you're right - I should have posted here.  We are now down to 4
dialin lines: 761-3000, 5041, 3411, and 3451.  Are you saying that the trunk
hunt isn't working at all, or just that all four lines were busy when you
tried to call?

response 34 of 68:

Oct 27 15:43 UTC 2003

I called Ameritech this morning to get them to fix the hunting on our lines.
(I was afraid that if I called on the weekend, I'd get someone who would
make the problem worse.)  I spoke with a gentleman named Jim, who checked
and found that all our numbers *except* 761-3000 had been programmed to
hunt.  He sent a request down to the programming department to fix things,
and they should be better in a few hours.  Please post here or send me mail
if there continue to be problems.

response 36 of 68:

Oct 27 17:24 UTC 2003

        I am currently on ttytf, but that might tell us if we hunted down
from -3000

response 38 of 68:

Oct 27 21:15 UTC 2003

Or you can dial 761-3000 with one phone, and dial it again with another.

response 40 of 68:

Oct 28 17:08 UTC 2003

  The /a partition, which contains your home directory, was temporarily
  full yesterday.  Perhaps your conference participation file was
  corrupted when picospan tried (and failed) to write it to a full
  filesystem?  (Just a guess and probably not a good one -- disk full
  errors occur so frequently on Grex (and before that, on M-Net) that
  I'd imagine picospan has to have a fairly robust way to deal with them.)

response 42 of 68:

Oct 28 18:33 UTC 2003

No, you're right, Mike.  Picospan doesn't handle it gracefully at all --
it truncates the participation file.

response 44 of 68:

Nov 4 08:05 UTC 2003

/d is almost full, too

response 46 of 68:

Nov 4 18:56 UTC 2003

I noticed this same thing. What is up with the birthday list in the 
motd? I see several birthdays listed for users that haven't used the 
system in ages (like griz), and many of us that came by Grex later in 
life aren't ever listed (like myself, for one). Does one have to be in 
the "inner circle" to matter?

response 48 of 68:

Nov 4 19:30 UTC 2003

Who do we provide that information to? I thought they picked it off 
your plan. Or did they run some kind of program at one point and then 
never ran it again. So now we're not on the list. so what gives?