| Previous | Contents | Index |
Automounting allows you to mount a remote file system on an as-needed basis. This means that the client automatically and transparently mounts a remote server path as soon as the user accesses the path name. Automounting is convenient for file systems that are inactive for large periods of time. When a user on a system invokes a command to access a remote file or directory, the automount daemon mounts the file and keeps it mounted as long as the user needs it. When a specified amount of time elapses without the file being accessed, it is dismounted. You can specify an inactivity period (5 minutes is the default), after which the software automatically dismounts the path.
You specify automounting and an inactivity interval with the qualifier /AUTOMOUNT=INACTIVITY:OpenVMS_delta_time.
The inactivity interval is the maximum inactive period for the mount attempt. When this period expires, the NFS client dismounts the path name as described below.
In this example, the client automounts directory /usr/webster residing on host robin onto the OpenVMS mount point DNFS67:. When it references the path name, the client keeps the path mounted unless it reaches an inactive period of 10 minutes, after which it dismounts the file system. With subsequent references, the client remounts the file system.
TCPIP> MOUNT DNFS67: /HOST="robin" - _TCPIP> /PATH="/usr/webster" /AUTOMOUNT=INACTIVITY=00:10:00 |
Background mounting allows you to retry a file system mount that initially failed. For example, you may have set mount points in your system startup command file so they are automatically mounted every time your system reboots. In this scenario, if the server is unavailable (because, for example, the server is also rebooting), the mount requests fail. With background option set, the client continues to try the mount after the initial failure. The client continues trying up to 10 times at 30-second intervals (default) or for the number of retries and interval you specify.
If you specify background mounting, you should also use the /RETRIES qualifier with a small nonzero number. This qualifier sets the number of times the transaction itself should be retried. Specify background mounting, along with the desired delay time and retry count parameters, with the /BACKGROUND=[DELAY:OpenVMS_delta_time, RETRY:n] qualifier.
For example, the following command attempts to mount in background mode, on local device DNFS4:, the file system /flyer, which physically resides on host migration. If the mount fails, the NFS client waits 1 minute and retries the connection up to 20 times.
TCPIP> MOUNT DNFS4: /HOST="migration" /PATH="/flyer" - _TCPIP> /BACKGROUND=(DELAY:00:01:00, RETRY:20) /RETRIES=4 |
If you use the /BACKGROUND qualifier, Compaq strongly recommends that
you also use the /RETRIES qualifier specifying a non-zero value. For If
you use the default value for /RETRIES (zero), the first mount attempt
can never complete except by succeeding, and the process doing the
mount will hang until the server becomes available.
17.3.4 Overmounting
Overmounting allows you to mount another path onto an existing mount point. Specify overmounting with the /FORCE qualifier. The client dismounts the original mount point and replaces it with a new one.
Mounting a higher or lower directory level in a previously used path is also an overmount. For example, an overmount occurs when you execute two MOUNT commands in the following order:
TCPIP> MOUNT DNFS123:[USERS.MNT] /HOST="robin" /PATH="/usr" %DNFS-S-MOUNTED, /usr mounted on _DNFS123:[USERS.MNT] TCPIP> MOUNT DNFS123:[USERS.MNT] /HOST="robin" - _TCPIP> /PATH="/usr/tern" /FORCE %DNFS-S-REMOUNTED, _DNFS123:[USERS.MNT] remounted as /usr/tern on ROBIN |
The second MOUNT command specifies a lower level in the server path.
This constitutes another path name and qualifies for an overmount.
17.3.5 Occluded Mounting
Occluded mounting allows you to mount a file system onto a client mount point that is higher or lower in the directory structure than an existing, active mount. This is different from overmounting because dismounting does not occur. Instead, the client occludes (hides from view) the subdirectory (or subdirectories) added to or dropped from the original mount specification when you perform a directory listing.
Specify an occluded mount with the /FORCE qualifier.
In the following example, the mount point specification was "backed up" one subdirectory from the previous one. If you enter the SHOW MOUNT command, both mounts are visible. However, if you enter DIRECTORY for DNFS2:[USERS.SPARROW], [.MNT] is no longer visible. To make this subdirectory visible again, issue the DISMOUNT command to dismount DNFS2:[USERS.SPARROW].
TCPIP> MOUNT DNFS2:[USERS.SPARROW.MNT] /HOST="birdy" /PATH="/usr" %DNFS-S-MOUNTED, /usr mounted on _DNFS2:[USERS.SPARROW.MNT] TCPIP> MOUNT DNFS2:[USERS.SPARROW] /HOST="birdy" /PATH="/usr" /FORCE %DNFS-S-MOUNTED, /usr mounted on _DNFS2:[USERS.SPARROW] -TCPIP-I-OCCLUDED, previous contents of _DNFS2:[USERS.SPARROW] occluded |
The following example shows a mount of UNIX directory /usr to the OpenVMS device and directory DNFS3:[0,0].
On the UNIX host, the directory listing looks like this:
unix% ls grebe wings pratincole |
To do the mount, enter:
$ TCPIP MOUNT DNFS3: /HOST="unix" /PATH="/usr" |
To check that the mount succeeded, enter:
$ TCPIP SHOW MOUNT DNFS3: /FULL . . . |
On the OpenVMS host, the directory listing looks like this:
$ DIRECTORY [0,0] Directory DNFS3:[000,000] GREBE.DIR;1 WINGS.DIR;1 PRATINCOLE.DIR;1 Total of 3 files. |
Additional qualifiers to the MOUNT command are described in the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual.
Part 6 describes how to set up and manage the printing services available with DIGITAL TCP/IP Services for OpenVMS.
Chapter 18 describes how to set up LPR/LPD, providing access to local and remote print queues.
Chapter 19 describes how to set up and manage the TELNET print symbiont (TELNETSYM). TELNETSYM provides remote print services that enable the use of standard OpenVMS printing features not available with LPR/LPD.
Chapter 20 describes how to set up and manage printing for PC-NFS client users.
The LPR/LPD service allows other network hosts to access queues on the server system and provides local access to queues on remote hosts. The remote print server and the client hosts must run Version 4.2 (or later) of the Berkeley Software Distribution line printer spooler software (lpd).
The line printer daemon (LPD) controls all printers and handles the following tasks:
This chapter describes how to set up and manage the LPR/LPD printing
service available with the DIGITAL TCP/IP Services for OpenVMS product.
See the DIGITAL TCP/IP Services for OpenVMS User's Guide for general information regarding usages and
complete command descriptions.
18.1 Reviewing Key Concepts
The LPR/LPD service allows other network hosts to access queues on the server system and provides local access to queues on remote hosts. The line printer daemon (LPD) is activated when you enter a print or LPR command. The daemon copies the file to the printer's spool directory and prints requests in the order in which they entered the queue. A copy of the file to be printed remains in the queue until the printer is ready to print it, then the LPD daemon removes the file from the spooling queue and sends it to the printer.
LPD uses the printcap database to process print requests. The printcap database, located in SYS$SPECIFIC:[TCPIP$LPD]:TCPIP$PRINTCAP.DAT, is an ASCII file that defines the print queues. The printcap entries are similar in syntax to the entries in a UNIX /etc/printcap file.
You configure printers by manually editing the printcap database and by creating the necessary spool directories and log files. Section 18.3.1 describes how to manually configure printers.
Alternately, you can use the printer setup program LPRSETUP to
configure or modify printers. The setup program creates spool
directories and log files based on the information you supply.
Section 18.3.2 describes how to use the printer setup program to
configure printers.
18.2 Configuring LPR/LPD
If you use the configuration procedure to configure LPR/LPD, the procedure completes the following tasks:
| Logical Name | Description |
|---|---|
| TCPIP$LPD_PRINTCAP | Database that maps queues and makes queues available. |
| TCPIP$LPD_SPOOL | Main spooling directory. |
| TCPIP$LPD_RETRY_INTERVAL | For outbound print jobs, time period between retries to print. |
| TCPIP$LPD_MAXIMUM_INTERVAL | For outbound print jobs, maximum time period that LPD retries to print if repeatedly unsuccessful. |
| TCPIP$LPD_LOGFILE | Name of the log file for the TCPIP$LPD_QUEUE, which precedes all inbound jobs. |
| TCPIP$LPD_PS_EXT |
Database that maps PS extensions
Used to configure systemwide PostScript options. Values for this logical name are as follows:
|
LPD uses the printcap database to process print requests. The printcap database, located in SYS$SPECIFIC:[TCPIP$LPD]:TCPIP$PRINTCAP.DAT, is an ASCII file that defines the print queues. The printcap entries are similar in syntax to the entries in a UNIX /etc/printcap file.
If you use the configuration procedure to configure LPD, this database is created for you. Unlike other database files, you can manually edit the printcap database to add or modify printer entries. Section 18.3.1 describes how to edit the printcap database.
Alternately, you can use the printer setup program
SYS$SYSTEM:TCPIP$LPRSETUP.EXE to configure or modify printers. This
program creates all necessary files and directories for you.
Section 18.3.2 describes how to use the printer setup program to
configure printers.
18.3.1 Manual Configuration
Printcap database entries identify the incoming and outgoing LPD queues on the local system. Each entry provides:
Entries for outgoing jobs also identify the name of the remote host and the printer on the remote host.
Printer characteristics are specified by 2-character mnemonic symbols and values that define the printer's configuration. Table 18-2 describes the printcap symbols.
| Symbol | Description |
|---|---|
| sd | Printer spool directory. |
| lf |
Specifies the error log file. This is optional. If you do not specify
an error log file, errors are logged to the operator console.
An error log can be shared by all local printers if you specify the same file in each printcap printer entry. |
| lp | Name of the local printer. |
| ps | LPD PrintServer extensions flag. |
| rm | Name of the remote host. |
| rp | Name of the remote printer. |
| fm | Printer form field. |
| pa | /PASSALL flag. |
| nd | /NODELETE flag. |
| cr | cr flag. |
| p1-p8 | /PARAMETER=(p1,...,p8) field. |
To make the printcap entries easier to read, use one symbol per line, placing a colon (:) at the start of each line and a colon and backslash (:\) at the end of the line to separate the symbols. The last printcap entry ends with a colon (:).
The following sample is an entry from the printcap database that identifies a local printer.
#
LOCAL1|local1:\
:lf=/SYS$SPECIFIC/TCPIP$LPD/LOCAL1.LOG:\
:lp=LOCAL1:\
:sd=/SYS$SPECIFIC/TCPIP$LPD/LOCAL1:\
:nd:
|
The following sample is a printcap entry that identifies a remote printer:
#
REMOTE1|remote1:\
:lf=/SYS$SPECIFIC/TCPIP$LPD/REMOTE1.LOG :\
:rp=REMOTE1 :\
:rm=HERMES :\
:sd=/SYS$SPECIFIC/TCPIP$LPD/ :
|
Each printer must have its own spool directory located under the SYS$SPECIFIC:[TCPIP$LPD] directory. The spool directory acts as a printer's spooling queue; it contains the files that are queued for printing on that particular printer. A printer spool directory should have the same name as the printer reference name and must be located on the machine to which the printer is attached.
Each printer should specify a spool directory even if the printer is connected to another machine or is on another network. You specify a spooling directory in the printcap database with the sd symbol. For example:
:sd=/SYS$SPECIFIC/TCPIP$LPD/LOCAL1: |
The LPD daemon records printer errors in a log file located in SYS$SPECIFIC:[TCPIP$LPD]. You can set up a separate log file for each printer or one to be shared by all local printers.
Specify the log file in the printcap database with the symbol lf. For example, to specify a log file for the print queue named LOCAL1, the printcap entry would be as follows:
:lf=/SYS$SPECIFIC/TCPIP$LPD/LOCAL1.LOG:\ |
To specify a log file that can be shared by all printers, specify the same file for each printer entry. For example:
:lp=LOCAL1:\ :lf=/SYS$SPECIFIC/TCPIP$LPD/TCPIP$LPD_LOGFILE.LOG:\ . . . :lp=LOCAL2"\ :lf=/SYS$SPECIFIC/TCPIP$LPD/TCPIP_LPD_LOGFILE.LOG: |
You can configure LPD to support remote printing on a system that does not implement the DIGITAL PostScript extensions. You do this for individual queues by adding a ps field in the queue's printcap entry with a value of non_PS. The printcap entry looks as follows:
:rm=Remote1 :ps=non_PS |
If you do not define a ps entry, LPD assumes the printer supports the DIGITAL PostScript extensions.
Note that you can also configure this option systemwide with the TCPIP$LPD_PS_EXT logical name. Values for this logical name are non_PS and LPS. See Table 18-1 for more information about the LPD logical names.
If a printcap entry does not have a ps field defined, LPD uses
the value you assigned with the logical name. If the logical name is
not defined, LPD uses PS extensions as the default.
18.3.2 Configuring Printers with LPRSETUP
This section describes how use the printer setup program, SYS$SYSTEM:TCPIP$LPRSETUP.EXE, to configure a printer directly connected to your computer. Similar to the UNIX /usr/sbin/lprsetup utility, you can also use this program to modify a printer's configuration or remove a printer.
Before running the printer setup program, you need the following information for each printer you want to configure:
The printer setup program performs the following:
Table 18-3 describes the LPRSETUP commands.
| Command | Description |
|---|---|
| add | Adds a printer name by which you want to identify the printer through the LPR command, for example, LPR -P printername. |
| delete | Removes an existing printer from your configuration. |
| view | Displays the contents of the current printcap database. |
| help | Displays online help about the LPRSETUP program. |
| exit | Exits from the LPRSETUP program. |
You can abbreviate any command option with its initial letter. Enter information at each prompt or press Return to accept the default. Enter a question mark (?) to obtain a description of the information requested at each prompt.
The following example illustrates how to use the printer setup program to configure a printer named LOCAL1:
$ RUN SYS$SYSTEM:TCPIP$LPRSETUP
TCPIP Printer Setup Program
Command < add delete view help exit >: add
Adding printer entry, type '?' for help.
Enter printer name to add : LOCAL1
Enter the FULL name of one of the following printer types:
remote local : local
Enter printer synonym:
Enter full file specification for spool directory
SPOOLER DIRECTORY 'sd' : [SYS$SPECIFIC:[TCPIP$LPD.LOCAL1]] ?
Enter full file specification for printer log file.
printer error log file 'lf' [SYS$SPECIFIC:[TCPIP$LPD]LOCAL1.LOG] ?
Enter the name of the printcap symbol you want to modify. Other
valid entry is :
'q' to quit (no more changes)
The names of the printcap symbols are:
sd for the printer spool directory
lf for the printer error log file
lp for the name of the local printer
ps for the LPD PrintServer extensions flag
rm for the name of the remote host
rp for the name of the remote printer
fm for the printer form field
pa for the /PASSALL flag
nd for the /NODELETE flag
cr for the cr flag
p1-p8 for the /PARAMETER=(p1,...,p8) field
Enter symbol name: q
Symbol type value
------ ---- -----
Error log file : lf STR /SYS$SPECIFIC/TCPIP$LPD/LOCAL1.LOG
Printer Queue : lp STR LOCAL1
Spool Directory : sd STR /SYS$SPECIFIC/TCPIP$LPD/LOCAL1
Are these the final values for printer LOCAL1 ? [y]
Adding comments to printcap file for new printer, type '?' for help.
Do you want to add comments to the printcap file [n] ? :
***********************************************
* TCPIP$LPD_STARTUP.COM TCPIP$LPD_PRINTCAP*
* and TCPIP$LPD_SHUTDOWN.COM *
* have been updated for this printer *
* *
* Set up activity is complete for this printer*
***********************************************
Command < add delete view help exit >: exit
|
The following example shows how to use the printer setup program to remove a printer from the printcap database:
Command < add delete view help exit >: delete
Deleting a printer entry, type '?' for help.
Enter printer name to delete (or view to view printcap file): LOCAL1
Symbol type value
------ ---- -----
Error log file : lf STR /SYS$SPECIFIC/TCPIP$LPD/LOCAL1.LOG
Printer Queue : lp STR LOCAL1
PS extensions flag: ps STR non_ps
Spool Directory : sd STR /SYS$SPECIFIC/TCPIP$LPD/LOCAL1
Delete LOCAL1, are you sure? [n] y
Deleted file: /SYS$SPECIFIC/TCPIP$LPD/LOCAL1.LOG
Deleted files from spooling directory: /SYS$SPECIFIC/TCPIP$LPD/LOCAL1
Removed spooling directory: /SYS$SPECIFIC/TCPIP$LPD/LOCAL1.DIR
Command < add delete view help exit >: exit
|
| Previous | Next | Contents | Index |