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-234          
 
Author Message
25 new of 234 responses total.
scott
response 75 of 234: Mark Unseen   Jul 18 21:04 UTC 1998

Oops, nobody announced it:

Grex was down from maybe midnight[?] to 9:10am this morning.
aruba
response 76 of 234: Mark Unseen   Jul 19 03:28 UTC 1998

uptime says:

 11:27pm  up 8 days, 13:18,  39 users,  load average: 1.28, 1.43, 2.38

Was Grex up, but not accessible?
scg
response 77 of 234: Mark Unseen   Jul 19 06:28 UTC 1998

The console terminal crashed, which dropped Grex into ROM monitor.  When that
happens, it's possible to tell Grex to resume where it left off, rather than
rebooting it.
aruba
response 78 of 234: Mark Unseen   Jul 19 14:52 UTC 1998

So uptime is not a reliable source of information on how long Grex has
been up? 

scott
response 79 of 234: Mark Unseen   Jul 19 16:10 UTC 1998

It generally is.  We should look into using a more reliable console PC.
tsty
response 80 of 234: Mark Unseen   Jul 20 08:53 UTC 1998

eieio ...no, what promted that question?
tsty
response 81 of 234: Mark Unseen   Jul 20 09:04 UTC 1998

oh, scg ... it was before i wnet to sleep ... and after i got up...which
may not be 36 hours, by count.
eieio
response 82 of 234: Mark Unseen   Jul 20 11:04 UTC 1998

Reference to a sign you posted on a particularly ornery machine once...
tsty
response 83 of 234: Mark Unseen   Jul 20 17:22 UTC 1998

expound please?
eieio
response 84 of 234: Mark Unseen   Jul 20 19:34 UTC 1998

The machine now lives somewhere along Platt Road...
rtgreen
response 85 of 234: Mark Unseen   Jul 21 00:17 UTC 1998

'..a more reliable console PC':  What are the requirements?  is it just
emulating a dumb terminal?  If so, I have several ADM-3a's and an IBM 3101
that I would be most willing to donate.
scott
response 86 of 234: Mark Unseen   Jul 21 00:37 UTC 1998

Well, it's an original IBM PC, and it seems to lock up about once a month.
We used to use big 60-line Ann arbor Ambassador terminals, but I think those
got too flaky to use.
davel
response 87 of 234: Mark Unseen   Jul 21 21:22 UTC 1998

Some phone line may be ringing open.  The last few times I've dialed in, it
rings several times, then rings differently (different rhythm, I think -
probably switching to another line), then connects.

This morning's crash garbaged my participation file.  Bleah.  But that was
quite a storm, and Grex was right to run & hide.   8-{)]
tendo
response 88 of 234: Mark Unseen   Jul 22 12:03 UTC 1998

why was grex not up yesterday? I really want to know.
bruin
response 89 of 234: Mark Unseen   Jul 22 12:13 UTC 1998

RE #88 Three words, tendo -- thunder and lightning.
tendo
response 90 of 234: Mark Unseen   Jul 22 12:32 UTC 1998

so grex hid from the storm?
dpc
response 91 of 234: Mark Unseen   Jul 22 17:54 UTC 1998

I added a bunch of lines to my .mailrc in an attempt to cut down on
those ridiculous large headers.  Typical lines I added were

discard Received:
discard Message-ID:

Unfortunately, these didn't work.  Is this a system problem or
my stupidity problem?
keesan
response 92 of 234: Mark Unseen   Jul 23 00:24 UTC 1998

How do you get the pine program to not list al the other recipients of e-mail?
Someone just sent me a change of address, but he also sent it to 100 or so
other people.
remmers
response 93 of 234: Mark Unseen   Jul 23 12:18 UTC 1998

Re resp:91 - I assume you're using the standard 'mail' program to
read mail. I can't find any mention of a 'discard' command in the
man page, so it appears not to be a system problem that it doesn't
work. This leaves the alternative...  :)

Something that does work here is the 'retain' command. The arguments
should be the list of headers that you *do* want to see. For example,
you could put this in your .mailrc:

        retain date to from subject

and 'mail' would show you just those four headers when it displays a
message.
dpc
response 94 of 234: Mark Unseen   Jul 23 14:45 UTC 1998

John, I am using the "discard" command at valerie's suggestion.
I tried it on M-Net, and it worked perfectly.  However, on M-Net
I did *not* have colons; on Grex I did.  Ergo, I'm going to delete
the colons.
        Thanx for letting me know about the retain command!
dpc
response 95 of 234: Mark Unseen   Jul 23 14:48 UTC 1998

Yep, deleting those colons did the trick!  Sometimes I'm so clever
I scare myself. 8-)
dpc
response 96 of 234: Mark Unseen   Jul 23 15:02 UTC 1998

Oh- I did encounter a *true* system problem late yesterday afternoon.
I dialed in on 761-3000, got a connection, entered my loginid and
password, and was promptly disconnected.  I got the same thing on
761-4931.
scott
response 97 of 234: Mark Unseen   Jul 23 16:05 UTC 1998

There was a vandal bothering us for a while then, then until a little after
6pm we had it closed to get some tracking done.
remmers
response 98 of 234: Mark Unseen   Jul 23 17:37 UTC 1998

Re resp:94 - Hm... My problem was that I was looking at the 'mailx'
man page, not 'mail'. The mail page documents 'discard', but the
mailx page does not. Odd - I thought they were the same program.
davel
response 99 of 234: Mark Unseen   Jul 27 23:11 UTC 1998

The motd states, at present, in part:
> Are you having a problem with some feature of Grex? Have you read the FAQ?
> It contains answers to most common questions, and can easily be seen on the
> web at http://www.cyberspace.org/faq.html or by typing the "faq" command.
> (Type !faq if you are at a prompt other than a shell prompt.)     -srw
However, running faq merely does nothing at all.  It's a link to
/usr/local/grex-scripts/faq, whose contents are the following:
> #!/bin/sh
> #
> # Display Grex FAQ sheet
> #
> ###menumore /usr/local/grexdoc/grex-faq
> 
Since the menumore line is commented out, it's not surprising that it
doesn't work, is it?
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-234          
Response Not Possible: You are Not Logged In
 

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