NAME¶

supfilesrv, supscan - sup server processes

SYNOPSIS¶

supfilesrv[-4] [-6] [-d] [-l] [-q] [-N] [-P] [-C MaxChildren]
supscan [-v] [-s] [collection] [basedir]

DESCRIPTION¶

Supfilesrvis the server processes used to interact withsupclient processes via the IP/TCP network protocol.This servernormally is expected to be running on server machines at all times.Each machine with files of interest to users on other machines isexpected to be a file server and should runsupfilesrv.

A file server machine will service requests for both "private" and"system" file collections.No special action is necessary to supportprivate collections, as the client user is expected to supply allnecessary information.For system collections, if the base directoryis not the default (see FILES below), an entry must be put intothe directory list file; this entry is a single text line containingthe name of the collection, one or more spaces, and the name of thebase directory for that collection.

Each collection should havean entry in the host list file; this entry is a single text linecontaining the name of the collection, one or more spaces, andthe name of the host machine acting as file server for that collection.

Details of setting up a file collection for the file server aredescribed in the manual entry forsup(1).

Supfilesrvgenerally runs as a network server process that listens for connections,and for each connection (double-)forks a process to handle the interactionwith the client.However, with the -d flag, no forking will take place:the server will listen for a network connection, handle it, and exit.This is useful for debugging the servers in "live" mode rather than asdaemons.

For debugging purposes, the -P "debugging ports" flag can be used.It will cause the selection of an alternate, non-privileged set ofTCP ports instead of the usual ports, which are reserved for theactive server processes. The -N "network debugging" flag can be usedto produce voluminous messages describing the network communicationprogress and status. The more -N switches that you use the more outputyou get. Use 3 (separated by spaces: -N -N -N) to get a complete recordof all network messages. Log messages are printed bysyslogondaemon.log .To suppresslog messages, the -q "quiet" flag can be used.

supfilesrvuses libwrap style access control (the /etc/hosts.allow and /etc/hosts.denyfiles) with service name "supfilesrv". The -l "log" flag turn on loggin ofaccepted connections (denied connections are always logged).

Normally thesupfilesrvwill only respond to 3 requests simultaneously, forking a childprocess for each client. If it gets additional requests it will respondwith the error FSSETUPBUSY. The -C MaxChildren switch can be usedto increase (or decrease) this number.

supfilesrvlistens to IPv4 listening socket by default.With the -6 flag, it will listen to IPv6 listening socket.For dual stack support you will want to run two instances ofsupfilesrv.

SUPSCAN¶

It is possible to pre-compile a list of the files in a collectionto makesupfilesrvservice that collection much faster. This can be done by runningsupscanon the desired collection on the repository machine. This produces alist of all the files in the collection at the time of thesupscan;subsequent upgrades will be based on this list of files rather thanactually scanning the disk at the time of the upgrade. Of course,the upgrade will consequently bring the client machine up to the statusof the repository machine as of the time of thesupscanrather than as of the time of the upgrade; hence, ifsupscanis used, it should be run periodically on thecollection.This facility is useful for extremely large file collectionsthat are upgraded many times per day, such as the CMU UNIX systemsoftware. The "verbose" flag-vwill causesupscanto produce output messages as it scans the files in the collection.The "system" flag-swill causesupscanto scan all system collections residing on the current host.Thebasedirparameter must be specified if the collection is a privatecollection whose base directory is not the default.

FILES¶

/usr

default base directory for a collection

/etc/supfiles/coll.dir

base directory list for system collections

/etc/supfiles/coll.host

host name list for system collections

<base-directory>/sup/<collection>/*

files used by file server (seesup(1))

<base-directory>/sup/<collection>/list

list file used bysupscanto create file list

<base-directory>/sup/<collection>/scan

file list created bysupscanfrom list file

SEE ALSO¶

sup(1)hosts_access(5)hosts_options(5)
The SUP Software Upgrade Protocol,S.A.Shafer, CMU Computer Science Dept., 1985.

DIAGNOSTICS¶

The file server places log messages on thestandard and diagnostic output files.The process name and processid number generally accompany each message for diagnostic purposes.

HISTORY¶

31-July-92 Mary Thompson (mrt) at Carnegie Mellon University

Removed references to supnameserver which has not existed fora long time. Update a few file names. Added -C switch.

21-May-87 Glenn Marcy (gm0w) at Carnegie-Mellon University

Updated documentation for 4.3; changed /usr/cmu to /usr/cs.

15-Jan-86 Glenn Marcy (gm0w) at Carnegie-Mellon University

Updated documentation; -s switch to supscan.

23-May-85 Steven Shafer (sas) at Carnegie-Mellon University

Supscan created and documented; also -N flag.

04-Apr-85 Steven Shafer (sas) at Carnegie-Mellon University

Created.