Path: utzoo!attcan!uunet!labrea!agate!ucbvax!tut.cis.ohio-state.edu!osu-cis!att!ihlpl!ihchk!ihtlt!kosman!kevin
From: kevin@kosman.UUCP (Kevin O'Gorman)
Newsgroups: unix-pc.bugs
Subject: Glitch in logging with PCOMM 1.2 (but overall hooray for same!)
Message-ID: <552@kosman.UUCP>
Date: 6 Feb 89 23:50:08 GMT
Organization: K.O.'s Manor - Vital Computer Systems, Oxnard, CA 93035
Lines: 27

I just got pcomm 1.2 loaded up with no problems.  I talk with my trailblazer
at all speeds, etc, etc..

However, when I tried to do a screen dump, it said it couldn't, which I
guessed meant the file had to already exist, so I touched it, and that
worked.

Next, I tried data logging, and I could not get that to work at all at first,
and there WAS NO ERROR MESSAGE.  The status line just wouldn't go to LOG ON.

It turns out that both problems were protection related.  I was running
pcomm from my Filecabinet directory (blush! yes, I use UA), which is
755 kevin users.  Pcomm is suid uucp bin, and cannot create files in that
directory.

This is easy to fix, of course, if you play as loose with protections as I
do. However, it could use an error message, and some warnings in the docs
about protections on the current working directory.  It would be nice if
the error message reminded you what directory we're talking about, too.

Otherwise, I love it, and I will finally get to throw away the phone manager,
which was only used for ATE anyway.  I do lots of calls to non-unix systems,
and I need to capture the data.  Nothing else I have would do it until
pcomm came along.  What's more, I can now try cranking this thing up to
19200, which is a real boon.

Once again, thanks, Emmet.  There ought to be an award for guys like you.