Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!cs.utexas.edu!asuvax!mcdphx!mcdchg!ddsw1!ddsw1!vpnet!hb
From: hb@vpnet.UUCP (hank barta)
Newsgroups: comp.unix.xenix
Subject: Re: xmodem transfers
Keywords: xmodem cu
Message-ID: <25c28971:527.2comp.unix.xenix;1@vpnet.UUCP>
Date: 28 Jan 90 08:00:11 GMT
References: <25bd1e45:527comp.unix.xenix@vpnet.UUCP> <1990Jan26.162447.3894@chi
Lines: 20

Leslie,
	You're absolutely right. Actually both copies of cu are
still there while running a remote command. I've done some more
exploration on this using umodem. This program has anoption which
allows it to open the (modem) tty device to perform the transfer
when it runs on the local system. However, when I run it, the open
fails on an access violation (EACCES).  This is, I guess, caused
either by the fact that cu has locked the device, or the program
doesn't have the correct acces priveleges for the device. (I
have very little experience programming UNIX so I'm probing
pretty murky waters here.)

To try and solve the problem, I have used chown to make uucp the
the owner of both /dev/tty2A and umodem. I have also used 
"chmod g-l /dev/tty2A" which, as near as I can tell, might cause
cu to not lock the device. These have not solved the problem.

I appreciate your alternate solutions. I was unable to find
uuencode on the remote system. Kermit is available (in binary 
format of course!)
					Thanks,
						Hank