lpsched(1M)                      DG/UX R4.11                     lpsched(1M)


NAME
       lpsched, lpshut, lpmove - start/stop the LP print service and move
       requests

SYNOPSIS
       /usr/lib/lp/lpsched
       lpshut
       lpmove requests dest
       lpmove dest1 dest2

DESCRIPTION
       Lpsched starts the LP print service; this can be done only by a user
       with appropriate privilege or lp.  On a generic DG/UX system,
       appropriate privilege is granted by having an effective UID of 0
       (root).  See the appropriateprivilege(5) man page for more
       information.

       On a system with DG/UX information security, appropriate privilege is
       granted by having one or more specific capabilities enabled in the
       effective capability set of the user.  See capdefaults(5) for the
       default capabilities for this command.

       On a DG/UX system with security features added, lpsched audits events
       associated with lp requests and printers.  Refer to DG/UX auditing
       documentation for more details.

       When mandatory access control (MAC) is present, lpsched supports MAC
       labeling.  All requests have an LUB and GLB label based on the files
       to be printed. These labels must fall within the MAC range of the
       destination in order to print.  Additionally, front and back banner
       pages are printed for each request.  The back banner pages are not
       always printed when a job is cancelled.  In the cases where standard
       lpsched prints a "cancel banner" page, trusted lpsched will also.

       lpshut shuts down the print service.  All printers that are printing
       at the time lpshut is invoked will stop printing.  When lpsched is
       started again, requests that were printing at the time a printer was
       shut down will be reprinted from the beginning.

       lpmove moves requests that were queued by lp between LP destinations.
       The first form of the lpmove command shown above (under SYNOPSIS)
       moves the named requests to the LP destination dest.  Requests are
       request-IDs as returned by lp.  The second form of the lpmove command
       will attempt to move all requests for destination dest1 to
       destination dest2; lp will then reject any new requests for dest1.

       Note that when moving requests, lpmove never checks the acceptance
       status [see accept(1M)] of the new destination.  Also, the request-
       IDs of the moved request are not changed, so that users can still
       find their requests.  The lpmove command will not move requests that
       have options (content type, form required, and so on) that cannot be
       handled by the new destination.

       If a request was originally queued for a class or the special
       destination any, and the first form of lpmove was used, the
       destination of the request will be changed to new-destination.  A
       request thus affected will be printable only on new-destination and
       not on other members of the class or other acceptable printers if the
       original destination was any.

       When mandatory access control (MAC) is present, lpmove will fail to
       move a request if the MAC label of the request is outside the MAC
       range of the new destination.

FILES
       /var/spool/lp/*

SEE ALSO
       accept(1M), lpadmin(1M).
       enable(1), lp(1), lpstat(1), capdefaults(5).


Licensed material--property of copyright holder(s)