les@chinet.chi.il.us (Leslie Mikesell) (02/05/91)
In article <1212@otello.sublink.org> venta@otello.sublink.org (Paolo Ventafridda) writes: >I need to set up a uucico call in master mode only. >i.e. i DON'T want to swap roles once my stuff is being sent. >Basically, i'd like to get a uucico session in master mode only, >and forget about the slave mode. I think the following entries in Permissions will do what you want: REQUEST=no And perhaps: SENDFILES=call >I tried to figure out how to do it with Permissions (hdb uucp), but >i couldn't come to anything useful. With Permissions you can >act just on files/mail already arrived (i.e. after a slave session). I think you are mistaken about this. However, you should note that the relevant Permissions entry is found by searching for a matching MACHINE=name entry when you are placing a call out, but by the LOGNAME=login_name on inbound calls. Thus you must have different machines use different login names if you want to set up different Permission entries for their inbound calls. If you are using nuucp as the login name, then you will get the permissions associated with the first entry for nuucp in Permissions. The REQUEST option applies to either inbound or outbound calls and determines whether you will allow their requests to be handled (i.e. in slave mode). The SENDFILES option is only significant for inbound calls (according to LOGNAME) and determines whether you will send work you have already queued on this connection or wait until you call them. Les Mikesell les@chinet.chi.il.us
time@tbomb.ice.com (Tim Endres) (02/05/91)
In article <1991Feb04.211030.5635@chinet.chi.il.us>, les@chinet.chi.il.us (Leslie Mikesell) writes: > The REQUEST option applies to either inbound or outbound calls and > determines whether you will allow their requests to be handled > (i.e. in slave mode). The SENDFILES option is only significant > for inbound calls (according to LOGNAME) and determines whether > you will send work you have already queued on this connection or > wait until you call them. I know it took me several times of reading this to realize that Les was saying what I was thinking. To make it more blunt for persons like myself, what Les was saying here is that UUCP allows a host to both send a file (S command) and request a file (R command). The send and request commands can be executed in either call out or call in cases, but a given host only *services* requests in SLAVE mode. The requestor is of course in MASTER mode. This way, my machine can call your machine and say "I am requesting file FILENAME please send it now". I do not need to execute a uucp command on the other host. The REQUESTS=yes/no entry in the permissions file determines if the host is allowed to make such requests. tim. ------------------------------------------------------------- Tim Endres | time@ice.com ICE Engineering | uupsi!ice.com!time 8840 Main Street | Voice FAX Whitmore Lake MI. 48189 | (313) 449 8288 (313) 449 9208
les@chinet.chi.il.us (Leslie Mikesell) (02/12/91)
In article <1CE00001.2n6sxi@tbomb.ice.com> time@ice.com writes: > >In article <1991Feb04.211030.5635@chinet.chi.il.us>, les@chinet.chi.il.us (Leslie Mikesell) writes: >> The REQUEST option applies to either inbound or outbound calls and >> determines whether you will allow their requests to be handled >> (i.e. in slave mode). The SENDFILES option is only significant >> for inbound calls (according to LOGNAME) and determines whether >> you will send work you have already queued on this connection or >> wait until you call them. >I know it took me several times of reading this to realize that Les >was saying what I was thinking. Actually, I was mislead by the documentation as well. From AT&T's Operation/System Administraton guide for SysV3.2 (386): "The REQUEST option specifies whether or not the remote machine can request to set up file transfers from your computer." Even though the rest of the context talked about the called machine requesting files to be transferred to it, I took the meaning to be that REQUEST referred to a command from the called machine requesting a transfer in either direction. I was wrong. >To make it more blunt for persons >like myself, what Les was saying here is that UUCP allows a host to >both send a file (S command) and request a file (R command). In fact, setting REQUEST=no means that any R commands from the remote are denied and discarded with an error message. (These are generated on the other machine with commands like: uucp your_machine!file /usr/spool/uucppublic to create a request for a remote file). >The send and request commands can be executed in either call out or >call in cases, but a given host only *services* requests in SLAVE mode. >The requestor is of course in MASTER mode. The calling machine starts out in MASTER mode, completes all the locally queued commands, and then the machines switch roles. The original question was about preventing the switch to slave mode, and now it appears that it can't be done. Setting SENDFILES=call on both machines might be what is really wanted, though. This will keep each machine from sending locally queued files back to the caller (that is, it will wait until it has placed its own call) but it requires the cooperation of the other site. >This way, my machine can call your machine and say "I am requesting >file FILENAME please send it now". I do not need to execute a uucp >command on the other host. The REQUESTS=yes/no entry in the >permissions file determines if the host is allowed to make such >requests. This is correct, but now I'm not sure what the original question was trying to accomplish. Les Mikesell les@chinet.chi.il.us