Using usblauncher to mount filesystems

The usblauncher service can mount the filesystems of attached USB devices based on the rules in a mountpoint file.

The usblauncher service reads either the default mcd mountpoint file (/etc/mcd.mnt) or another file specified with the -M option in the command line that started the service. Basically, usblauncher performs the function of the MOUNT_FSYS rule in the mcd configuration file while using the standard mechanism of mount to do the actual mounting.

Preventing mcd from mounting USB devices

To use the usblauncher auto-mounter feature when your system runs mcd, you must do one of the following two actions:

These actions ensure that usblauncher and mcd don't try to mount the same filesystems, which will happen if both processes are tasked with assigning mountpoints for the same USB-related /dev entries. For more information on mcd and its configuration file, refer to the mcd entry in the Utilities Reference.

Disabling usblauncher auto-mounter

If your system setup requires you to use mcd for mounting all devices, you can disable the usblauncher auto-mounter feature by specifying an empty mountpoint file with the -M option. With no matching mountpoint entries for any attached devices, usblauncher won't try to mount any filesystems.

This strategy is handy if you need to mount the filesystems of both USB and non-USB devices and you prefer to use a common service (mcd) for all mounting operations. Unfortunately, usblauncher will no longer be able to log the mount attempts and publish accurate mnt_status values through PPS.