3.5 Setting up iPrint on the NSS File System

It is now possible to host iPrint configuration and data on an NSS Volume. In a standard single server setup, you can continue to host iPrint on your default native Linux file system or you can host iPrint on the NSS file system.

In a cluster setup, we recommend making iPrint available in an OES 11 SP2 NSS Cluster.

NOTE:When you create a volume, ensure that it has enough space to host all your driver needs.

Use iprint_nss_relocate script to host iprint on NSS file system in a standalone or cluster setup. This script performs the following actions:

3.5.1 Running the iprint_nss_relocate script

To run the iprint_nss_relocate script:

  1. Go to the /opt/novell/iprint/bin folder on your OES11 server.

  2. Run the following command at the prompt:

    ./iprint_nss_relocate -a <admin dn> -p <password> -n <NSS path> [-l cluster[-c] [-w]]

    For example:./iprint_nss_relocate -a cn=admin,o=novell -n /media/nss/DATA -c o=Novell,t=iPrint_Tree -w o=Novell,t=iPrint_Tree -l cluster

If you do not specify the password in the command, you are prompted to enter the password when the script runs. Refer to the following table for details on the options.

Option

Value

-a

Admin DN in LDAP format

-p

Password for the Admin user

-n

NSS Path with no trailing slash

IMPORTANT:When you specify the path, ensure that there are no trailing slashes after the NSS path.

For example: The path should be specified as /media/nss/NSSVOl1 and not as /media/nss/NSSVOL1/.

-l Cluster (Optional)

Use this parameter only when you want to achieve clustering on NSS file systems. For more details on clustering, see Section 8.0, Configuring iPrint with Novell Cluster Services.

IMPORTANT:Use the cluster keyword with the -l option. Do not replace the cluster keyword with a cluster object name.

-c (Optional)

Specify the container FDN in LDAP format where the iPrint LUM object already exists or should be created.

All the iPrint nodes on an NSS Cluster should share the iPrint LUM objects (iprint user and iprintgrp group) and should be in the same container. If the nodes are in different containers, you should specify the existing iPrint LUM objects' context on subsequent nodes where ipring_nss_relocate is running. To specify the context, give the -c option in the command. Do not choose the context where the non-user object named iPrint already exists.

-w (Optional)

Specify the container FDN in LDAP format where Apache LUM objects exist.