The script is now executable for all users and will be run as root. A corresponding 

umount script is very simple, as shown in Example 7 14.

Example 7 14   Script doumount to handle problems with pam_mount 

#!/bin/sh  x

# 

# umount script to fix pam_mount.so functionality

# 

# smbumount is allowed for user

/usr/bin/smbumount $1

This file has to have the same properties as the domount script.

Once the scripts have been installed with the proper owner and permissions, the 

pam_mount.conf file has to be changed to use these scripts. To enable this we 

make the following changes to the /etc/security/pam_mount.conf file:

smbmount /usr/local/bin/domount

umount   /usr/local/bin/doumount

7.5  How to use network printers in the domain

Being able to use existing printers is one of the most important pre conditions for 

a new type of client in any environment. We do not want to keep separate 

printing environments for every type of client.

This means that the Linux client will have to use the (network) printers available 

in the domain. We can achieve this in two ways:

Print directly to the printer using its network interface.

Print to the printer using the Windows print server and its SMB interface.

Both options are available using CUPS from the Linux client. We suggest using 

the second option, however, since all prints in the domain (and user's 

environment) will be on equal footing. This means there are just prints and not 

Windows prints and Linux prints.

You need to be running CUPS on the Linux client. This can be checked by:

/etc/init.d/cups status

This should return that CUPS is running and give its PID. If not it can be started 

using:

/etc/init.d/cups start

 Chapter 7. Integration how tos 

147