To check the print server type for a Solaris 2.x client with a Solaris 2.x print server:

1.  On the print client, become superuser.

2.  Type lpsystem -l and press Return. Check the output to make sure that the print server is identified as type s5 (for Solaris 2.x). In the following example, the print server oak is properly identified as type s5:

# lpsystem -l
System:                 oak
Type:                  s5
Connection timeout:        never
Retry failed connections:   after 1Ø minutes
Comment:                 none
#

If the print server is not identified correctly, type lpsystem -t S5 print-server-name and press Return, as follows:

# lpsystem -t S5 oak
#

Use the following steps to check the print queue on the print client:

1.  Type cd /var/spool/lp/requests/system-name and press Return. This directory contains a record of print requests still in the queue.

2.  Type ls -l and press Return. A list of the print jobs appears on-screen.

3.  For the print job you want to check, type lpstat -o request-id and press Return. In the following example, the job is queued successfully:

# cd /var/spool/lp/requests/clobber
# ls -l
total 12
-rw-rw----   1 lp   lp          43 May 22 19:44 11-Ø
# lpstat -o pinecone-11
pinecone-11         root           364   May 22 19:59
#

If the job is not queued successfully, the client-server connection may be faulty. Use the following steps to make sure that the client-server connection is not faulty:

1.  On the print client, type tail /var/lp/logs/lpsched and press Return. The output of this command shows whether lpsched can connect to the print server. In the following example, the log does not indicate any problems:

# tail /var/lp/logs/lpsched
09/24 14:53:53: Print services started.
09/24 18:05:40: build info: 07/15/97:21:39:52
09/24 18:05:40: Print services started.
09/25 08:19:53: build info: 07/15/97:21:39:52
09/25 08:19:53: Print services started.
09/25 09:09:28: build info: 07/15/97:21:39:52
09/25 09:09:28: Print services started.
09/25 17:04:34: Print services stopped.
09/26 08:52:57: build info: 07/15/97:21:39:52
09/26 08:52:57: Print services started.
#

2.  If the connection is not being made, on the print server, type lpstat -t and press Return. The output of this command shows you whether the print server is operating properly. In the following example, printers pinecone and red are up and running on the print server:

pine% lpstat -t
scheduler is running
system default destination: pinecone
device for pinecone: /dev/term/a
pinecone accepting requests since Thu May 23 2Ø:56:26 PDT 1991
printer red is idle. enabled since Sun May 19 17:12:24 PDT 1991.
 available.
printer pinecone now printing pinecone-314. enabled since Fri May 24
 16:1Ø:39 PDT 1991. available.
pinecone-129        root         488   May 23 2Ø:43 filtered
pine%

3.  On the print server, type tail /var/lp/logs/lpsched and press Return. Examine the lpsched log to see if the print server is connecting to the client. If there is no entry, or if the server cannot complete the connection to the print client, lpsched is not transmitting correctly. The following example shows the log for two jobs. The first job, from the system elm, completed successfully. The second job could not complete because the print server could not connect to the system opus.

papers% tail /var/lp/logs/lpsched
Ø5/17/93 Ø9:39 c   834 elm Starting.
Ø5/17/93 Ø9:39 c   834 elm Normal process termination.
Ø5/17/93 Ø9:41 p   162 <none> Started child for elm, pid = 9Ø2
Ø5/17/93 Ø9:41 c   9Ø2 elm Starting.
Ø5/17/93 Ø9:41 c   9Ø2 elm Connected to remote child.
Ø5/17/93 Ø9:41 c   341 opus Could not connect to remote child.
Ø5/17/93 Ø9:51 c   341 opus Could not connect to remote child.
Ø5/17/93 1Ø:Ø1 c   341 opus Could not connect to remote child.
Ø5/17/93 1Ø:11 c   341 opus Could not connect to remote child.
Ø5/17/93 1Ø:21 c   341 opus Could not connect to remote child.
papers%

4.  On the print server, type lpsystem -l and press Return. Check the output to make sure that the print client is correctly identified as type s5. In the following example, the print client oak is configured correctly:

# lpsystem -l
System:                     clobber
Type:                       s5
Connection timeout:         never
Retry failed connections:   after 1Ø minutes
Comment:                    none

If the print client configuration is incorrect, type lpsystem -t s5 client-system-name and press Return, as follows:

# lpsystem -t s5 oak

5.  On the print server, type sacadm -l and press Return. Make sure that the port monitor and network listen service are set up properly. The following example shows a print server that is configured correctly:

# sacadm -l
PMTAG        PMTYPE     FLGS RCNT STATUS         COMMAND
tcp  listen    - 9999 ENABLED  /usr/lib/saf/listen tcp #
#

6.  Type pmadm -l and press Return. The following example shows a print server that is configured for all three types of services:

# pmadm -l
PMTAG        PMTYPE          SVCTAG          FLGS ID    <PMSPECIFIC>
tcp  listen lp - root  - - p - /var/spool/lp/fifos/listenS5 #
tcp      listen   lpd          -  root
 x000202038194143a0000000000000000 - p -
/var/spool/lp/fifos/listenBSD #
tcp      listen   Ø     -  root
 x00020ACE8194143a0000000000000000 - c -
/usr/lib/saf/nlps_server #
#

If the service and port monitors are not configured correctly, refer to the instructions earlier in this chapter for how to configure SAF for printers.