Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!hao!gatech!udel!princeton!mccc!pjh From: pjh@mccc.UUCP (Peter J. Holsberg) Newsgroups: comp.unix.questions Subject: Re: 7300 to 3b2 Message-ID: <267@mccc.UUCP> Date: 1 Mar 88 15:07:40 GMT References: <3504@killer.UUCP> Reply-To: pjh@mccc.UUCP (Peter J. Holsberg) Distribution: na Organization: The College on the Other Side of US Route 1 Lines: 36 Keywords: uucp uux In article <3504@killer.UUCP> bobc@killer.UUCP (Bob Calbridge) writes: |We have seven 7300's attached to a 3B2 via standard serial lines. Normal |communication is done through the "cu" command. However, since these |7300's are used by students, we are trying to devise a way do some file |exchanging without having the students become too involved in the workings |of unix. We tried using "uucp" and at first the problem was an improper |system name in the PC's L.sys file. Having taken care of that we tried |again. This time we received no error message but the file didn't show |up in the 3B2. The question is if there is a way to track where the |file went, if anywhere. We need some help. Please point us in the |right direction. Bob, We have an identical setup! Use "uuto !" to send to the 3B2, where is the file on the 7300, id the 3B2's name, and is the user's login. Then have the user type "tail -f /usr/spool/uucp/LOGFILE" and watch the progress of the call and xfr. Next, the user should logon to the 3B2, and use "uupick" to retrieve his files from the public directory. 3B2-->7300 requires issuing a uucp command from the 7300. Watchout for file and directory permisssions! The file to be xfrd must be r for all, and the directory that it resides in must be rx for all. -- Peter Holsberg UUCP: {rutgers!}princeton!mccc!pjh Technology Division CompuServe: 70240,334 Mercer College GEnie: PJHOLSBERG Trenton, NJ 08690 Voice: 1-609-586-4800