Is UUX looking too closely at its arguments?

[Leslie Mikesell]

In article <1991Apr9.161715.5495 at jwt.UUCP> john at jwt.UUCP (John Temples) writes:

>I have a print program on a remote machine which I try to access with:
>uux "remote!print -f/some/path/name !local_file"

>This fails on the remote machine, saying "file access denied to user."
>Without the -f/path, it works fine.  The -f is simply the full path
>name of the local file to be shown on the banner by the print program;
>the print program does not try to access the file with that path name.
>Substitute -f!some!path!name, and it works fine.  Am I correct in
>assuming that uux is looking at the arguments to my program when it
>shouldn't be, and if so, can I make it stop?  This is an SVR3.2 system.
>TFM does not show -f to be a command line switch to uux.

I don't think you can make the remote uuxqt stop looking at the command
line arguments, but you should be able to make them acceptable by
giving the sending machine r/w permission to the directories in
question.   If you aren't too paranoid about what the other machine
might send, putting READ=/ WRITE=/ in the permissions entry ought
to do it.  And if you already allow COMMANDS=ALL, it doesn't make any
difference anyway since the command could cd first.
Just keep in mind that the Permissions entries are found by the
MACHINE= field on outgoing calls, but by the LOGNAME= field on
inbound calls.  I like to make every machine have a unique login
name to maintain some sanity about this.

Les Mikesell
  les at chinet.chi.il.us