jeffh@weycord.WEYCO.COM (07/31/88)
I just spent a few days trying to "take" a file in cu. My system at home is a 386 XENX box and the remote system is a 350 running HP-UX 6.0. Due to the fact that I just installed the XENIX system and have been running the HP-UX system for a couple of years I was sure the XENIX system had a problem- NOT SO SURE NOW... A local company running XENIX allowed me to try calling in to their system and "put" and "take" a few files- all worked as expected. Well, I went back to the HP-UX machine (this time a s800) and tried again- same thing. I could "put" files but couldn't "take" files. At the suggestion of a local friendly SE I tried the same thing in the bourne shell. IT WORKED! The following is a log of the of the session: ( I'm already logged into the HP-UX box from the XENIX box) ---------------------------------------------- %~%take test.c mesg n;echo '~>':test.c;cat test.c;echo '~>';mesg y "~>:test.c" (remove the quotes) (next the file is echoed to the screen) "~>" (again- remove the quotes) can't divert ~> ---------------------------------------------- I was root on the XENIX machine and my directory was /tmp so access was NOT the problem. Notice that the "can't divert" has a void file name. What is bizzare about this whole mess is it works if I'm in the bourne shell on the UP-UX machine and it doesn't if I'm in the "C" shell. Oh ya, "put" and "take" work just fine when you "cu" to the XENIX machine from the HP-UX machine. And "put" works just fine when you "cu" to the HP-UX machine from the XENIX machine. I've got an easy work-around (use the bourne shell) so this note is posted cause I'd just like to understand why!!! -- Jeff (Spectra Software) Harrell