NAME

lpsbootd − unified boot daemon for PrintServer printers

SYNOPSIS

lpsbootd [ −b ] [ −t ] [ −l loglevel ] [ −x debuglevel ] [ −L logfile ] [ −T tftpdir ] [ −F odbfile ] [ −n ]

DESCRIPTION

lpsbootd is used to perform the initial booting of PrintServer printers that are defined on the local host using the lpssetup script.  This program must be run under the root account, since privileged UDP ports must be assigned to the process. 

In normal operation lpsbootd is automatically launched by the PrintServer Management Client software (the lpsad daemon), typically when the local host is booted.  That is, you normally never have to explicitly execute lpsbootd on the local host. 

The lpsbootd daemon will, by default, service boot requests from PrintServer printers on UDP port 170.  It is also possible for lpsbootd to function as a BOOTP and/or TFTP server, however the daemon will only service BOOTP requests for PrintServer printers defined on the local host; any BOOTP request coming from a client not defined in the LPS Object Database (/etc/lpsodb) will be ignored. 

A PrintServer printer shipped after the LPS V5.1 release have boot ROMs that enable the printer to broadcast BOOTP and TFTP requests to UDP port 170; lpsbootd is designed to work specifically with these printers.  PrintServer printers with older boot ROMs will only request booting on the standard BOOTP port (UDP port 67) and the standard TFP port (UDP port 69). 

The lpsbootd daemon is able to support the booting of older printers when the -b and -t options are specified.  See the PrintServer Management Guide for details on how to configure the PrintServer software to enable lpsbootd to act as a BOOTP and/or TFTP server for these older models. 

OPTIONS

−bEnable processing of BOOTP requests on the standard BOOTP port (UDP port 67).  This option would be used if a bootpd daemon is not configured for the local host (typically in the /etc/inetd.conf file) and you need to support booting of older PrintServer printers.  Note that BOOTP requests from devices will not be serviced by lpsbootd unless the device is a PrintServer printer defined on the local host.  Use this option if the only devices requiring BOOTP support are older PrintServer printers. 
 

−tEnable processing of TFTP requests on the standard TFTP port (UDP port 69).  This option would be used if a tftpd daemon is not configured for the local host (typically in the /etc/inetd.conf file) and you need to support booting of older PrintServer printers. 
 

−l loglevel
Set the logging verbosity level to loglevel.  Possible values range from 0 to 9; the default value is 0. 
 

−x debuglevel
Set the debugging verbosity level to debuglevel.  Possible values range from 0 to 9; the default value is 0.  This option only has effect on DEBUG versions of the software. 
 

−L logfile
Write log output to the path specified by logfile.  By default all log output is written to the $LPSLOG/lpsbootd.log file, where $LPSLOG is the path of the standard logging directory as defined when the PrintServer software was installed.  Normally $LPSLOG is defined to be the /var/adm or /var/adm/log directory. 
 

−T tftpdir
The path of the directory in which the daemon assumes files reside for TFTP requests.  If this option is specified, then the daemon will do a chroot(2) to this directory before servicing TFTP requests, in a manner similar to the standard tftpd(8) daemon.  This option is only used in conjunction with the -t option.
 

−F odbfile
Specifies the path of the LPS Object Database file to be used by the daemon. The default path is /etc/lpsodb.
 

−nDo not operate the daemon detached from the controlling terminal.  This option is rarely used. 
 
 

EXAMPLES

Use this command for quiet operation in which only newer PrintServer printers are to be serviced:

% lpsbootd

Use this command to service BOOTP and TFTP requests for newer PrintServer printers, and to service BOOTP requests from older printers (while still using the standard tftpd(8) daemon for TFTP requests for those printers):

% lpsbootd −b

Use this command to service BOOTP and TFTP requests for newer PrintServer printers, and to service both BOOTP and TFTP requests from older printers (Note: you can not use tftpd(8) in this case):

% lpsbootd −b −t

Use this command to increase the log output from the daemon in order to troubleshoot problems (adding other options as necessary):

% lpsbootd −l 9 −x 9
 

RESTRICTIONS

The lpsbootd daemon must be executed under the root account. 

If the -b option is used, then only BOOTP requests from PrintServer printers defined on the local host will be serviced; all other requests will be ignored.  Note that lpsbootd does not use the standard /etc/bootptab file in any way. 

If the -t option is used, then the standard tftpd(8) daemon should not be configured to run on the local host, either explicitly or through invocation by the inetd(8) daemon. 
 

ENVIRONMENT

The lpsbootd daemon uses the LPS Object Database (typically /etc/lpsodb) to determine which PrintServer printers will be serviced.  The ethernet address (and optionally the DECnet address) for each printer must be entered when the printer is configured using the lpssetup script. 

The daemon will terminate operation upon one of the following signals: HUP, INT, QUIT, TERM. 
 

FILES

/etc/lpsodb The default LPS Object Database file. 

$LPSLOG/lpsbootd.log The log file used by the daemon. 
 

SEE ALSO

lpsad(8), PrintServer Management Guide
 

DIAGNOSTICS

Almost all log messages are prefixed by the name of the daemon and a timestamp.  This message prefix is not shown in the diagnostic messages below. 

Unable to open socket number: Permission denied
Either the daemon is not running under the root account, or some other process (possibly another copy of the lpsbootd daemon) currently has the port assigned. 

Failure to generate logfile stream:  Permission denied
The log file could not be opened.  The daemon is probably not running under the root account.

Cannot get broadcast address for interface interface
The specified interface may be the local IP loopback interface, in which case the message should be ignored.  Any other interface mentioned may currently be experiencing network problems. 

Missing ethernet address for PrintServer name
The PrintServer printer name does not have an ethernet address assigned to it.  Use the lpssetup script to associate the proper ethernet address to the printer. 

Cannot open configuration file path
The configuration file path could not be opened.  If the permission is denied, then the daemon is probably not running under the root account.  If the file does not exist, then the file must be regenerated using the lpssetup script. 

Error in converting host entry for object name
A summary message stating that PrintServer printer name has one or more errors in its definition such that the daemon will not be able to process requests for the printer.  Examine the messages immediately preceding this message to determine the exact reason(s). 
 

BUGS

The log file can get quite messy if multiple instances of the daemon are started at the same time. 
 

AUTHOR

Digital Equipment Corporation. 

  —  LPS V5.1  —  6 Jan 1995