lsof /usr/sbin/lsof

fsck /sbin/fsck

losetup /sbin/losetup

unlosetup /sbin/losetup  d

smbmount /usr/bin/smbmount

umount   /usr/bin/smbumount

volume * smb smb3lab26 & /home/&/domainshare uid=&,dmask=0750    

This enables debugging on pam_mount. Mount points are created when 

non existent and the share that will be mounted is indicated in the last line.

The asterisk near the beginning of the last line in the example above indicates 

that this volume is mounted for every user. The ampersand (&) in the definition is 

expanded to the user name of the user logging in. So the volume line in 

Example 7 12 on page 144 tells pam_mount to mount a share named after the 

user name from server smb3lab26 onto mount point 

/home//domainshare. The options indicate that the mount should be 

owned by the indicated uid and have permissions as indicated by dmask.

Attention:

 In some cases the pam_mount module will fail to setuid root, which 

means that normal 

mount

 commands will fail with and 

only root can do that

message. This is the case for Red Hat Desktop.

Possible workaround for pam_mount failing to setuid root

In this case you will find errors in the logs (/var/log/messages, most likely) that 

look like:

pam_mount: error setting uid to 0

Or:

pam_mount: mount: only root can do that

When these messages are present, this means that pam_mount is not working 

using the normal mount tools. A workaround can be created where the normal 

mount

 command is not used, but a script that will call 

smbmount

. Since the 

smbmount

 and 

smbumount

 are allowed to be used by normal users, this will work. 

We give an example of a possible script in Example 7 13 on page 146.

Another possible problem when mounting shares from a domain is that the 

ampersand (&) in the pam_mount.conf file expands to the entire user name, 

including the domain name and the winbind separator. As we stated in 7.2,  How 

to use winbind to make domain users known locally  on page 136, the best 

winbind separator in a Linux environment is a plus sign (+). This, however, is an 

illegal character in a share name under Windows. This means that if we want to 

use pam_mount to mount a share that has the user name in it, we have to get rid 

 Chapter 7. Integration how tos 

145