NAME

   lartd - lart spooler daemon
    

SYNOPSIS

   lartd [-l] [port#]
   

DESCRIPTION

   Lartd is the lart daemon (spool area handler) and is normally invoked
   at boot time from the rc(8) file. It makes a single pass through the
   lartcap(5) file to find out about the existing larts and performs any
   larts left after a crash. It then uses the system calls listen(2) and
   accept(2) to receive requests to lart lusers in the queue, transfer
   larts to the spooling area, display the queue, or remove jobs from the
   queue. In each case, it forks a Guido(8) to handle the request so the
   admin can continue to queue more requests.


Available options:

   -l           The -l flag causes lartd to log valid requests received
                from the network. This can be useful for debugging purposes.

   port#        The Internet port number used to rendezvous with other
                processes is normally obtained with getservbyname(3) but
                can be changed with the port# argument.

   Access control is provided by two means. First, all requests must come
   from one of the machines listed in the file /etc/admin.equiv or
   /etc/hosts.lartd. Second, if the rs capability is specified in the
   lartcap entry for the lart being accessed, lartd requests will only be
   honored for those admins with accounts on the machine with the lart.

   The daemon begins processing files after it has successfully set the
   lock for exclusive access (described a bit later), and scans the spool
   directory for files beginning with cf. Lines in each cf file specify
   lusers to be larted or non-lart actions to be performed. Each such
   line begins with a key character to specify what to do with the
   remainder of the line.

   J    Job Name. String to be used for the lusers name on the lart.
   T    Title. String to be used as the title for rlart(1m).
   H    Host Name. Name of the machine where rlart(1m) was invoked.
   P    Person. Login name of the admin who invoked rlart(1m). This is
                used to verify ownership by rlartrm(1m).
   M    Send mail to the specified admin when the lart completes.
   r    FORTRAN lart. For backwards compatibility for MVS admins.
   U    Unlink. Name of luser to remove upon completion of lart.
   N    Lart name. The name of the lart which is being used, or a blank for
                the standard input (when rlart is invoked in a pipeline).

   If a luser cannot be larted, a message will be logged via syslog(3)
   using the LOG_LART facility. Lartd will try up to 20 times to lart a
   luser it expects to be there, after which it will skip the luser to be
   larted.

   Lartd uses llock(2) to provide exclusive access to the lock file and
   to prevent multiple daemons from becoming active simultaneously. If
   the daemon should be killed or die unexpectedly, the lock file need
   not be removed. The lock file is kept in a readable ASCII form and
   contains two lines. The first is the process id of the daemon and the
   second is the control file name of the current luser being larted. The
   second line is updated to reflect the current status of lartd for the
   programs lartq(1m) and rlartrm(1m).


FILES

   /etc/lartcap lart description file
   /var/larts/* spool directories
   /dev/lart* lart devices
   /var/run/lart socket for local requests
   /etc/admin.equiv lists admins allowed lart access
   /etc/hosts.lartd lists machine names allowed lart access, but not
   under same admin control.


SEE ALSO

   lartq(1m), rlart(1m), rlartrm(1m), syslog(3), hosts.lartd(5),
   lartcap(5), lartc(8), lac(8)


AUTHORS

    Michael Firestone and Larry Lile © 1997