erict@flatline.UUCP (J. Eric Townsend) (08/15/89)
Recently upgraded to 3.5, and found more problems. Sigh. I did have this solved for 3.0... Basically, I have an entry for a news/uucp connection. I can uuto it, and news seems to work fine both ways. I can't, however, uuto from it to here.. Here's the Permissions entry. MACHINE=uhnix1 \ LOGNAME=uhnix1 \ REQUEST=yes SENDFILES=yes \ READ=/usr/spool WRITE=/usr/spool \ Note that I don't limit the commands, and that I give it *all of spool* to be able to write to. I still get, however: uucp uhnix1 (8/14-23:53:23,2889,0) REMOTE REQUESTED (uhnix1!/cs3e/com6/net/part0.Z --> flatline!~/receive/erict/uhnix1/ (com6)) uucp uhnix1 (8/14-23:53:23,2889,0) PERMISSION (DENIED) etc. From uhnix1, I did: uuto part0.Z flatline\!erict From flatline, uuto foo uhnix1\!com6 works just fine. -- J. Eric Townsend Johnny Lydon *IS* the next uunet!sugar!flatline!erict incarnation of The Doctor.. com6@uhnix1.uh.edu 511 Parker #2, Houston, Tx 77007 EastEnders Mailing list: eastender@flatline.UUCP
harrys@tons61.UUCP (Harry Skelton) (08/18/89)
In article <2328@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes: > >Recently upgraded to 3.5, and found more problems. Sigh. >I did have this solved for 3.0... > [ information about commands deleted ] >Note that I don't limit the commands, and that I give it *all of spool* >to be able to write to. I still get, however: >uucp uhnix1 (8/14-23:53:23,2889,0) REMOTE REQUESTED (uhnix1!/cs3e/com6/net/part0.Z --> flatline!~/receive/erict/uhnix1/ (com6)) >uucp uhnix1 (8/14-23:53:23,2889,0) PERMISSION (DENIED) > >etc. From uhnix1, I did: >uuto part0.Z flatline\!erict > >From flatline, >uuto foo uhnix1\!com6 >works just fine. Looks like 1) the home directory of the host is not in /usr/spool/whatever ? 2) UUCP/HDB is using the default COMMANDS option which may not include 'uucp'? 3) directory permissions for read is ok for /usr/spool (which is why the first part of the uuto worked) but can't write. Your unix has a top down permissions problem ? i.e. /usr is 755 and /usr/spool is 777 and you can't write due to /usr ? I would check your default commands for 'uhnix1'. Also check the home directory of 'uhnix1' and the permissions. I think that should solve it. Me? I have a brain damaged CCI Unix UUCP (OLD L.sys type).... ANYONE AT CCI READING THIS???
rich@jolnet.ORPK.IL.US (Rich Andrews) (08/23/89)
In article <29@tons61.UUCP> harrys@tons61.UUCP (Harry Skelton) writes: >In article <2328@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes: >> >>etc. From uhnix1, I did: >>uuto part0.Z flatline\!erict I think the way that you invoked uuto is where your problem is. The man page for uuto says uuto {filename} machine!user. It mentions nothing about machine\!user or machine/!user. I have seen that construct fail more times than not. It appears that there were security problems in uucp and that those problems have been fixed. rich -- Any opinions expressed are my own. Now, for a limited time, they can be yours too, for the incredible price of only $19.95. Simply send $19.95 (in Alterian dollars) to ...killer!jolnet!rich or rich@jolnet.orpk.il.us.
erict@flatline.UUCP (J. Eric Townsend) (08/23/89)
In article <1372@jolnet.ORPK.IL.US> rich@jolnet.orpk.il.us (Rich Andrews) writes: >>In article <2328@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes: >>>etc. From uhnix1, I did: >>>uuto part0.Z flatline\!erict >I think the way that you invoked uuto is where your problem is. >The man page for uuto says uuto {filename} machine!user. >It mentions nothing about machine\!user or machine/!user. "\!" is how you type a "!" when you're using /bin/ksh. The "!" alone is a command for the shell, so you have to escape it. -- Good ole' boys, J. Eric Townsend tellin' lies, unet!sugar!flatline!erict com6@uhnix1.uh.edu 'bout time EastEnders Mailing list: eastender@flatline.UUCP I got wise. -- B-52's.
les@chinet.chi.il.us (Leslie Mikesell) (08/24/89)
In article <2352@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes: >>It mentions nothing about machine\!user or machine/!user. >"\!" is how you type a "!" when you're using /bin/ksh. The "!" >alone is a command for the shell, so you have to escape it. Perhaps you mean csh. Typing ! at ksh gives: /bin/ksh: !: not found Any of the common shells would remove the \ before uuto sees it, though. Les Mikesell
rich@jolnet.ORPK.IL.US (Rich Andrews) (08/25/89)
In article <2352@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes: >In article <1372@jolnet.ORPK.IL.US> rich@jolnet.orpk.il.us (Rich Andrews) writes: >>>In article <2328@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes: >>>>etc. From uhnix1, I did: >>>>uuto part0.Z flatline\!erict >>I think the way that you invoked uuto is where your problem is. >>The man page for uuto says uuto {filename} machine!user. >>It mentions nothing about machine\!user or machine/!user. > >"\!" is how you type a "!" when you're using /bin/ksh. The "!" >alone is a command for the shell, so you have to escape it. Gee, what command is that? I use ksh all the time on several machines and never had to escape "!". rich andrews -- "Hey Rocky, watch me pull a rabbit out of my hat." Bullwinkle Moose "oh...a wise guy....Come here....I'll murder ya..." Moe Howard "I'm hunting wabbits...." Elmer Fudd "If I could typ I'd be dangerous" Rich Andrews
erict@flatline.UUCP (J. Eric Townsend) (08/25/89)
In article <9338@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes: >In article <2352@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes: >>"\!" is how you type a "!" when you're using /bin/ksh. The "!" >>alone is a command for the shell, so you have to escape it. >Perhaps you mean csh. Typing ! at ksh gives: > /bin/ksh: !: not found Yep. You're correct. I meant csh. Also, I solved the problem. It was a typo I'd made along the lines of: MACHINE=foo \ [various permissions] \ # ^ -- Here's the problem! MACHINE=BAR [various *different* permissions] As I understand it, this caused uucp to read bar's permissions in as well, and used those instead of the permissions I'd declared for foo. At least I *think* that's what happened. I know it worked when I removed the "\" after foo's permissions. -- Good ole' boys, J. Eric Townsend tellin' lies, unet!sugar!flatline!erict com6@uhnix1.uh.edu 'bout time EastEnders Mailing list: eastender@flatline.UUCP I got wise. -- B-52's.
dts@quad.uucp (David T. Sandberg) (08/26/89)
In article <1399@jolnet.ORPK.IL.US> rich@jolnet.orpk.il.us (Rich Andrews) writes: :In article <2352@flatline.UUCP> erict@flatline.UUCP (J. Eric Townsend) writes: :>"\!" is how you type a "!" when you're using /bin/ksh. The "!" :>alone is a command for the shell, so you have to escape it. : :Gee, what command is that? I use ksh all the time on several machines :and never had to escape "!". Maybe he's thinking of csh, where "!" is a very important metacharacter, of course. Ksh (and sh, for that matter) do have the "$!", which is the PID of the last background job, but to my knowledge that's the only place that "!" has any special meaning to ksh. -- David Sandberg - Quadric Systems "As of Friday, August 25, 1989, PSEUDO: dts@quad.uucp Triton is a Place." ACTUAL: ..uunet!rosevax!sialis!quad!dts