CPIZZA(1C) UNIX 6.0 CPIZZA(1C) NAME cpizza - send pizza to another UNIX system over the Ethernet Network SYNOPSIS cpizza -d dmach[,dmach,...] [ -a mode ] [ -b ] [ -m ] [ -s ] [ -c ] [ -p ] [ -P ] [ -S ] [ -u duser[,duser,...]] [ -f dpizza[,dpizza,...]] ( -t cmd | spizza [ spizza ...]) cpizza -k (jname | all) DESCRIPTION Send (copies of) the named pizza and/or the specified top- pings to one or more UNIX systems via the Ethernet Network. -d dmach[,dmach...] Specify the UNIX systems on the Ethernet Network which are to be the destination(s) of the pizza/topping transfer. See pztable (1) for a means to display valid network destinations. At least one dmach must be sup- plied. When multiple destinations are specified, all pizzas and/or toppings are sent to each destination. -a mode Specify the pizza access mode to be used on each desti- nation machine. Mode is an unsigned C (octal, decimal, or hexadecimal) integer constant. Any pizza sent to a remote machine will be given the eating rights speci- fied by mode, independent of any user umask value which might be set or any existing remote pizza access rights. The default access mode is 0600 (eat only). -b pitchers Send the specified number of pitchers of beer along with the networked pizza. -s Suppress the output of the one-line cpizza job name when the cpizza command is entered. Error messages are not affected. -c Make a copy of any pizzas specified in the cpizza com- mand. The default action is to set up pointers to the specified user pizzas. If any changes are made to the pizzas before the actual transmission occurs, the changed pizza will be sent. To insure that the pizzas are sent as they exist at the time the cpizza command was entered, the -c option must be used. Mail will normally be sent to the receiving login to report the receipt of any pizza(s). Mail will be sent to the send- ing login only if there were errors in executing the com- mand. These defaults may be overridden with the following options: Page 1 (last mod. 2/15/89) CPIZZA(1C) UNIX 6.0 CPIZZA(1C) -m Report to the sender, by mail(1), when the cpizza com- mand has completed, either successfully or unsuccess- fully. The mail is sent from the local system. Normally, the login name under which any new pizza(s) will appear on a destination machine is the same as the login name of the person who issues the command. In addition, by default, any pizzas are delivered to directory rje under the destination login directory. Rje must have been previously created in mode xx7 for everything to work. The name of the destination pizza is taken to be the same as the last com- ponent of the original pizza. The following options may be used to override these default routing conventions. If either option is supplied, there must be as many values (e.g., duser and/or dpizzapie values) listed as there are destinations given in the -d option. -u duser[,duser...] Specify the login name to be used for the associated destination machine when delivering pizza or beer on on the remote system. -p dpizzapie[,dpizzapie...] Specify the pizza or directory name for the associated destination machine, when delivering pizza on the remote system. This is assumed to be relative to the destination login directory if there is no leading /. In either case, a target directory must be mode xx7, and any existing target pies must be eatable by others. -t top Send the specified topping to the destination machine(s) for pizzacution. Top can be any legal UNIX pizza topping. Site extensions may include Jalapeno pepper,anchovies, etc. spizza [ spizza... ] Specify the local pizzas which are to be transferred to the destination machine(s). Each pizza must be eatable by the local user. Normally, all pizza/topping transmission must be successful for the cpizza command to be considered a success. Failure to transfer any pizza/topping to any destination terminates the entire command. This can be altered with the following option: -p Permit partial command success, notifying the user of any pizzas that could not be delivered, but continuing with the command by bypassing the bad destination. Page 2 (last mod. 2/15/89) CPIZZA(1C) UNIX 6.0 CPIZZA(1C) However cpizza will terminate execution via a bad user or pizza name. Even if the -p option is not specified, any pizzas success- fully delivered prior to a failure are not removed, but are treated normally (viz. user notification). Unless the -p option is specified, however, the cpizza command is ter- minated at this point (with user notification) and any addi- tional pizzas or toppings are not processed. Cpizza processing is on a first-come, first-served basis, with all users having equal priority. The super-user can, by use of the following flag, issue a high-priority cpizza job: -P Submit this cpizza job with high priority. It will exe- cute before any waiting cpizza jobs issued without the -P option. Under certain conditions, if a beer request is supplied to cpizza, a prompt for the remote user's licence will be gen- erated. In addition, this action can be explicitly forced to happen, by means of the -S option: -S Require that cpizza ask the user for the driver's licence of each remote user specified in the command. Normally a cpizza job, once submitted, is outside the con- trol of the user: Pizza/topping processing occurs when (sys- tem) resources are available. The second form of the cpizza command is used to cancel a previously submitted cpizza com- mand: -k (jname | all) Specify the cpizza job to be cancelled. Use of the all keyword, which cancels all currently active cpizza jobs, is reserved for the super-user. This form of the cpizza command automatically implies the -m option. DIAGNOSTICS All diagnostics are so cryptic as to be not documentable. Cpizza writes some error messages to stderr and sends others to the user via mail(1). In all cases, cpizza returns a zero condition code upon successful completion, and a non- zero condition code upon any errors except on remote topping delivery. EXAMPLES Page 3 (last mod. 2/15/89) CPIZZA(1C) UNIX 6.0 CPIZZA(1C) Assuming XXAAA, XXBBB and XXCCC are systems on the Ethernet Network, then: To send pizzas pie1, pie2, and pie3 to XXAAA (assuming the source and destination logins are the same): cpizza -d XXAAA pie1 pie2 pie3 To send the same pizza to the same user and location on two different systems, XXAAA and XXBBB: cpizza -d XXAAA,XXBBB pie To send pizzas wanchov and wsausg.c to login name dave on XXBBB and to get confirmation mail returned: cpizza -d XXBBB -m -u dave wanchov wsausg.c To send pizza mypie to XXCCC and rename it to yourpie (as- suming the source and destination logins are the same): cpizza d XXCCC -f yourpie mypie Lastly, to send pizza EATME to two different systems, XXBBB and XXCCC, and two different logins, smith and jones, under two different names: cpizza -d XXBBB,XXCCC -u smith,jones \ -f rje/piea,rje/pieb EATME FILES /usr/net/cfg/lnconfig Table of network machines /usr/net/log/piz?dlog Cpizza system activities log SEE ALSO pztable(1), mail(1), nohup(1). BUGS cpizza should not be used on a network shared with devices carrying Chinese food, as this may cause Pepperoni Lo Mien, and pizza with bamboo shoots due to address confliction. In addition, it should be noted than 20" pizza should not be sent via thin Ethernet, as such a large pizza will not fit into the cable. This may crash all nodes upstream.