Gerald Carter
October 2002

# Samba Printing Internals

## Abstract

The purpose of this document is to provide some insight into Samba's printing functionality and also to describe the semantics of certain features of Windows client printing.

## Printing Interface to Various Back ends

Samba uses a table of function pointers to seven functions. The function prototypes are defined in the `printif` structure declared in `printing.h`.

- retrieve the contents of a print queue

- pause the print queue

- resume a paused print queue

- delete a job from the queue

- pause a job in the print queue

- result a paused print job in the queue

- submit a job to the print queue

Currently there are only two printing back end implementations defined.

- a generic set of functions for working with standard UNIX printing subsystems

- a set of CUPS specific functions (this is only enabled if the CUPS libraries were located at compile time).

## Print Queue TDB's

Samba provides periodic caching of the output from the "lpq command" for performance reasons. This cache time is configurable in seconds. Obviously the longer the cache time the less often smbd will be required to exec a copy of lpq. However, the accuracy of the print queue contents displayed to clients will be diminished as well.

The list of currently opened print queue TDB's can be found be examining the list of tdb_print_db structures ( see print_db_head in printing.c ). A queue TDB is opened using the wrapper function printing.c:get_print_db_byname(). The function ensures that smbd does not open more than MAX_PRINT_DBS_OPEN in an effort to prevent a large print server from exhausting all available file descriptors. If the number of open queue TDB's exceeds the MAX_PRINT_DBS_OPEN limit, smbd falls back to a most recently used algorithm for maintaining a list of open TDB's.

There are two ways in which a a print job can be entered into a print queue's TDB. The first is to submit the job from a Windows client which will insert the job information directly into the TDB. The second method is to have the print job picked up by executing the "lpq command".

    /* included from printing.h */
    struct printjob {
    	pid_t pid; /* which process launched the job */
    	int sysjob; /* the system (lp) job number */
    	int fd; /* file descriptor of open file if open */
    	time_t starttime; /* when the job started spooling */
    	int status; /* the status of this job */
    	size_t size; /* the size of the job so far */
    	int page_count;	/* then number of pages so far */
    	BOOL spooled; /* has it been sent to the spooler yet? */
    	BOOL smbjob; /* set if the job is a SMB job */
    	fstring filename; /* the filename used to spool the file */
    	fstring jobname; /* the job name given to us by the client */
    	fstring user; /* the user who started the job */
    	fstring queuename; /* service number of printer for this job */
    	NT_DEVICEMODE *nt_devmode;
    };

The current manifestation of the printjob structure contains a field for the UNIX job id returned from the "lpq command" and a Windows job ID (32-bit bounded by PRINT_MAX_JOBID). When a print job is returned by the "lpq command" that does not match an existing job in the queue's TDB, a 32-bit job ID above the <*vance doesn't know what word is missing here*> is generating by adding UNIX_JOB_START to the id reported by lpq.

In order to match a 32-bit Windows jobid onto a 16-bit lanman print job id, smbd uses an in memory TDB to match the former to a number appropriate for old lanman clients.

When updating a print queue, smbd will perform the following steps ( refer to `print.c:print_queue_update()` ):

1. Check to see if another smbd is currently in the process of updating the queue contents by checking the pid stored in `LOCK/printer_name`. If so, then do not update the TDB.

2. Lock the mutex entry in the TDB and store our own pid. Check that this succeeded, else fail.

3. Store the updated time stamp for the new cache listing

4. Retrieve the queue listing via "lpq command"

5.     	foreach job in the queue
       	{
       		if the job is a UNIX job, create a new entry;
       		if the job has a Windows based jobid, then
       		{
       			Lookup the record by the jobid;
       			if the lookup failed, then
       				treat it as a UNIX job;
       			else
       				update the job status only
       		}
       	}

6. Delete any jobs in the TDB that are not in the in the lpq listing

7. Store the print queue status in the TDB

8. update the cache time stamp again

Note that it is the contents of this TDB that is returned to Windows clients and not the actual listing from the "lpq command".

The NT_DEVICEMODE stored as part of the printjob structure is used to store a pointer to a non-default DeviceMode associated with the print job. The pointer will be non-null when the client included a Device Mode in the OpenPrinterEx() call and subsequently submitted a job for printing on that same handle. If the client did not include a Device Mode in the OpenPrinterEx() request, the nt_devmode field is NULL and the job has the printer's device mode associated with it by default.

Only non-default Device Mode are stored with print jobs in the print queue TDB. Otherwise, the Device Mode is obtained from the printer object when the client issues a GetJob(level == 2) request.

## ChangeID and Client Caching of Printer Information

[To be filled in later]

## Windows NT/2K Printer Change Notify

When working with Windows NT+ clients, it is possible for a print server to use RPC to send asynchronous change notification events to clients for certain printer and print job attributes. This can be useful when the client needs to know that a new job has been added to the queue for a given printer or that the driver for a printer has been changed. Note that this is done entirely orthogonal to cache updates based on a new ChangeID for a printer object.

The basic set of RPC's used to implement change notification are

- RemoteFindFirstPrinterChangeNotifyEx ( RFFPCN )

- RemoteFindNextPrinterChangeNotifyEx ( RFNPCN )

- FindClosePrinterChangeNotify( FCPCN )

- ReplyOpenPrinter

- ReplyClosePrinter

- RouteRefreshPrinterChangeNotify ( RRPCN )

One additional RPC is available to a server, but is never used by the Windows spooler service:

- RouteReplyPrinter()

The opnum for all of these RPC's are defined in include/rpc_spoolss.h

Windows NT print servers use a bizarre method of sending print notification event to clients. The process of registering a new change notification handle is as follows. The 'C' is for client and the 'S' is for server. All error conditions have been eliminated.

    C:	Obtain handle to printer or to the printer
    	server via the standard OpenPrinterEx() call.
    S:	Respond with a valid handle to object

    C:	Send a RFFPCN request with the previously obtained
    	handle with either (a) set of flags for change events
    	to monitor, or (b) a PRINTER_NOTIFY_OPTIONS structure
    	containing the event information to monitor.  The windows
    	spooler has only been observed to use (b).
    S:	The <* another missing word*> opens a new TCP session to the client (thus requiring
    	all print clients to be CIFS servers as well) and sends
    	a ReplyOpenPrinter() request to the client.
    C:	The client responds with a printer handle that can be used to
    	send event notification messages.
    S:	The server replies success to the RFFPCN request.

    C:	The windows spooler follows the RFFPCN with a RFNPCN
    	request to fetch the current values of all monitored
    	attributes.
    S:	The server replies with an array SPOOL_NOTIFY_INFO_DATA
    	structures (contained in a SPOOL_NOTIFY_INFO structure).

    C:	If the change notification handle is ever released by the
    	client via a FCPCN request, the server sends a ReplyClosePrinter()
    	request back to the client first.  However a request of this
    	nature from the client is often an indication that the previous
    	notification event was not marshalled correctly by the server
    	or a piece of data was wrong.
    S:	The server closes the internal change notification handle
    	(POLICY_HND) and does not send any further change notification
    	events to the client for that printer or job.

The current list of notification events supported by Samba can be found by examining the internal tables in srv_spoolss_nt.c

- printer_notify_table[]

- job_notify_table[]

When an event occurs that could be monitored, smbd sends a message to itself about the change. The list of events to be transmitted are queued by the smbd process sending the message to prevent an overload of TDB usage and the internal message is sent during smbd's idle loop (refer to printing/notify.c and the functions send_spoolss_notify2_msg() and print_notify_send_messages() ).

The decision of whether or not the change is to be sent to connected clients is made by the routine which actually sends the notification. ( refer to srv_spoolss_nt.c:recieve_notify2_message() ).

Because it possible to receive a listing of multiple changes for multiple printers, the notification events must be split into categories by the printer name. This makes it possible to group multiple change events to be sent in a single RPC according to the printer handle obtained via a ReplyOpenPrinter().

The actual change notification is performed using the RRPCN request RPC. This packet contains

- the printer handle registered with the client's spooler on which the change occurred

- The change_low value which was sent as part of the last RFNPCN request from the client

- The SPOOL_NOTIFY_INFO container with the event information

A `SPOOL_NOTIFY_INFO` contains:

- the version and flags field are predefined and should not be changed

- The count field is the number of entries in the SPOOL_NOTIFY_INFO_DATA array

The `SPOOL_NOTIFY_INFO_DATA` entries contain:

- The type defines whether or not this event is for a printer or a print job

- The field is the flag identifying the event

- the notify_data union contains the new valuie of the attribute

- The enc_type defines the size of the structure for marshalling and unmarshalling

- (a) the id must be 0 for a printer event on a printer handle. (b) the id must be the job id for an event on a printer job (c) the id must be the matching number of the printer index used in the response packet to the RFNPCN when using a print server handle for notification. Samba currently uses the snum of the printer for this which can break if the list of services has been modified since the notification handle was registered.

- The size is either (a) the string length in UNICODE for strings, (b) the size in bytes of the security descriptor, or (c) 0 for data values.