|
|
| Author |
Message |
| 25 new of 227 responses total. |
pfv
|
|
response 125 of 227:
| 
Jan 23 03:41 UTC 2000 |
"-f" merely specifies a file - which is what procmail shoves stuff
into.
|
pfv
|
|
response 126 of 227:
|
Jan 23 14:51 UTC 2000 |
OK, I went - this time - searching thru .procmailrc and
from that to ~pfv/Mail/mbox.. 'Lo...!
I'd never touched procmail, so.. I followed it's pointing finger
and 'mbox' was there! (And I had several days mail I hadn't known
about).
The part that makes me REALLY confused is this:
1) the above 'mbox' has been around for almost a year now;
2) Even empty, elm was working right;
3) the "~pfv/mail/HOLD" file has a few letters I've been
saving, but:
A) they ALWAYS BEFORE were listed in 'mbox' - just older.
I must need a lot more coffee - this makes no sense at all.
|
pfv
|
|
response 127 of 227:
|
Jan 23 15:11 UTC 2000 |
OK, here's the scoop: I just read the new mail, and deleted 'em all..
1) No mention of those other messages I 'HOLD' (weird);
2) left elm & then came back..
!myelm
Can't open '/a/p/f/pfv/Mail/mbox' for reading! [No such file or directory]
!
THAT is what is different with the new version of elm: before it
would come up, but show nothing in the list. Now it refuses to
come up.
|
dpc
|
|
response 128 of 227:
|
Jan 23 18:48 UTC 2000 |
I'm having a repeated problem connecting to Grex. Just now (and
once before) when I dial 761-3000 I get a *huge* pile of electronic
junk on my screen, complete with chimes. When I hang up and
dial 761-4931, everything is fine. This is an *intermittent*
problem. Normally everything works fine on 761-3000. However,
apparently there is a modem "below" -3000 and "above" -4931
which needs a lobotomy.
|
keesan
|
|
response 129 of 227:
|
Jan 23 21:53 UTC 2000 |
When I did a r n in Music, with two new items, it whizzed through the first
one into the second without giving me a chance to read anything in the first
item. Did the same previously with some conference a little while ago.
|
scott
|
|
response 130 of 227:
|
Jan 24 15:35 UTC 2000 |
One of the modems is connecting but not getting a prompt. I'm watching to
see which one it is.
|
tpryan
|
|
response 131 of 227:
|
Jan 24 17:03 UTC 2000 |
re 130: I think I had that problem last night. On 761-3000 and
761-5041, I connected but got no message (not even the Grex is down
message).
|
scott
|
|
response 132 of 227:
|
Jan 24 21:32 UTC 2000 |
I've swapped ports on the line that wasn't behaving.
|
eeyore
|
|
response 133 of 227:
|
Jan 24 22:25 UTC 2000 |
I had problems getting in again today....dialed, got most of the way through
the "startup music", and then just started beeping. Happened twice.
|
tpryan
|
|
response 134 of 227:
|
Jan 25 02:59 UTC 2000 |
re 132: Thank YOu.
|
don
|
|
response 135 of 227:
|
Jan 25 15:48 UTC 2000 |
Found something interesting. Someone was sending me tels yesterday. I finished
talking with him and logged out, but I forgot to type "bye" at the login
prompt so I was still connected to the port. The guy sent me two more tels
while I was logged out. I take it this means that tel looks for ports rather
than uids?
|
mcnally
|
|
response 136 of 227:
|
Jan 25 19:09 UTC 2000 |
Unix, and Unix programs, are very file-oriented. Programs like tel,
write, talk, work by manipulating a special file-like object called
a pty, which represents the device (or port) through which you are
connected.
|
mdw
|
|
response 137 of 227:
|
Jan 26 09:24 UTC 2000 |
tel (& write & friends) look at /etc/utmp to decide if you're still
logged in. telnetd doesn't erase the entry in utmp until you
disconnect, so it's not totally surprising someone was able to write
you. telnetd does make an effort to turn write perms off, but evidently
it & tel don't have the same understanding about how write perms work.
|
janc
|
|
response 138 of 227:
|
Jan 28 04:40 UTC 2000 |
Basically tel thinks that write perms are determined by group-write bit
on the pty. This is probably what telnetd thinks too.
However, Orville write allows a few exceptions - conditions where you
can write people whose permissions are theoretically off. One case is
if you had set "mesg ne" and had a .yeswrite file. Another case is if
you had sent a telegram to this person not more than 4 minutes before.
There is a 4 minute window in which 'tel' lets you reply to telegrams,
even if the sender's permissions are off. Probably the latter is what
happened to you. An interesting bug, but not a very serious or fixable
one.
|
aruba
|
|
response 139 of 227:
|
Feb 4 21:34 UTC 2000 |
Was Grex down earlier today? I couldn't get in.
|
scott
|
|
response 140 of 227:
|
Feb 4 23:09 UTC 2000 |
inetd had died.
|
prp
|
|
response 141 of 227:
|
Feb 9 20:56 UTC 2000 |
The Picospan help command is broken again. (Still?) "Help index" fails,
even though index is listed as one of the things one can get help about.
Also I could not find the list of fair-whitness commands.
The help text also referneces /usr/forum/cluster, which does not exist.
|
prp
|
|
response 142 of 227:
|
Feb 9 21:16 UTC 2000 |
Also the picospan command "join share" fails.
|
i
|
|
response 143 of 227:
|
Feb 10 02:13 UTC 2000 |
The "share conference" is just a stub to ease access to PicoSpan
conferences outside of grex. Connecting & activation can only be
done by a root, and there are thorny security issues regardless....
don't count on ever seeing it in use.
Admitting that i'm *not* very knowledgable about it, the PicoSpan
help system has always struck me as a bit unfinished & unpolished.
I just keep poking around when i can't seem to find things in it,
and they usually turn up. "help morecommands" and "help set" are
good places to start reading up on fw stuff.
|
keesan
|
|
response 144 of 227:
|
Feb 11 18:58 UTC 2000 |
Jim just fixed my problem with Ymodem batch not working for upload on
one computer, by changing comports. Changing modems did not do it.
Odd symptom. It worked fine for download. Anyone have any idea why?
|
pfv
|
|
response 145 of 227:
|
Feb 11 19:00 UTC 2000 |
ummm...
Because you configured the MODEm WRONG, (hence the comport
success).
|
keesan
|
|
response 146 of 227:
|
Feb 11 19:18 UTC 2000 |
The modem was working just fine on the original comport for quite a long time,
then one day it suddenly would not upload Ymodem batch. It always worked
fine for Kermit in both directions. This is an old computer, we already had
to replace the floppy drive and video card in it. Parts do wear out.
|
gull
|
|
response 147 of 227:
|
Feb 11 20:31 UTC 2000 |
Being able to download, but not upload, is often a symptom of running with
no hardware handshaking. Some older modems have it turned off by default.
|
keesan
|
|
response 148 of 227:
|
Feb 11 23:08 UTC 2000 |
Jim turned it off by choice. He says he also changed the modem, but simply
replacing the modem did not fix the problem, he also had to change the com
port. I don't know why he turned it off (hardware handshaking). The external
modem is working with hardware handshaking turned off via software, he may
have tried another internal modem in the same com port. I will ask. Ymodem
worked in another computer with hardware handshaking turned off so we did nto
suspect this. Complicated. Thanks.
|
davel
|
|
response 149 of 227:
|
Feb 12 02:46 UTC 2000 |
Re 141 (way back there): "Help index" has, I think, been broken since I was
first on Grex - as are a few other help things (at least a few). I've
complained about a number over the years. I think that these are just text
files, & ought to be fixable ...
|
