Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ivman(8) [suse man page]

IVMAN(8)						      System Manager's Manual							  IVMAN(8)

NAME
ivman - volume manager SYNOPSIS
ivman [ -sd ] [ --nofork ] [ -c <directory> ] DESCRIPTION
Ivman, or Ikke's Volume Manager, is a daemon to handle the mounting of media as they are inserted/attached to the system. It can also be used to execute arbitrary commands when a device with certain properties is added to the system (Windows autoplay style functionality), and to execute arbitrary commands when device properties change. Ivman uses HAL to monitor the state of your system's hardware. OPTIONS
-s or --system Start Ivman in system-wide mode. This is the default if running Ivman as root. When this option is specified, Ivman reads from the system-wide configuration directory ( usually /etc/ivman/ ); if this option is not specified, Ivman reads from ${HOME}/.ivman/ instead. Either of these locations may be overridden with the -c option. Other behaviour may differ slightly when running in sys- tem-wide mode. Don't use this option unless you know you need it. --nofork Force Ivman not to daemonize, regardless of settings in IvmConfigBase.xml. Useful for capturing debugging output. -d or --debug Force Ivman to give debugging output, regardless of settings in IvmConfigBase.xml. -c <directory> or --confdir <directory> Force Ivman to load configuration files from the specified directory. DETAILS
Ivman is a flexible device manager, allowing users to run arbitrary commands when devices are added/removed, when device properties change, and when devices emit conditions. For automount purposes, Ivman should be run once from a system-wide init script and once per user session (e.g., create a link to /usr/bin/ivman in ~/.kde/Autostart or put an entry for /usr/bin/ivman in gnome-session-manager). When a device is attached, Ivman will call pmount or mount to mount the device. If pmount is used, it will mount the device readable and writeable only for the current user; if no per-user instance of Ivman is running, the device will be mounted read/write for everyone in the same group as is required to use the pmount command, and read-only for everyone else. If regular mount is used, then an fstab entry must exist in /etc/fstab for the device to be mounted, and the settings given in that fstab entry will be used for the mount. Ivman is supplied with sensible default configuration files for volume management, but autoplay functionality has no default actions; you will need to edit ${HOME}/.ivman/IvmConfigActions.xml(5) or /etc/ivman/IvmConfigActions.xml(5) to specify some programs to execute. The syntax of this file and the other Ivman configuration files are specified in their own manpages. FILES
/etc/ivman/IvmConfigActions.xml actions to perform when media is inserted /etc/ivman/IvmConfigBase.xml options affecting the running of Ivman /etc/ivman/IvmConfigConditions.xml actions to perform when devices emit conditions /etc/ivman/IvmConfigProperties.xml actions to perform when device properties change SEE ALSO
IvmConfigActions.xml(5), IvmConfigBase.xml(5), IvmConfigConditions.xml(5), IvmConfigProperties.xml(5) BUGS
Hopefully, none :-) But there could be some still lurking. If you encounter a bug, please forward details to rohan.pm@gmail.com or add it to the bug tracker at the project's Sourceforge page, http://sourceforge.net/projects/ivman 9 December 2005 IVMAN(8)

Check Out this Related Man Page

pumount(1)						      General Commands Manual							pumount(1)

NAME
pumount - umount arbitrary hotpluggable devices as normal user SYNOPSIS
pumount [ options ] device DESCRIPTION
pumount is a wrapper around the standard umount program which permits normal users to umount removable devices without a matching /etc/fstab entry. pumount also supports encrypted devices which use dm-crypt and have LUKS metadata. If a LUKS-capable cryptsetup is installed, pumount will umount the mapped device instead and call cryptsetup to close the decrypted device afterwards. pumount expects the device as its only argument. This will umount device from a directory below /media if policy is met (see below). Please note that, as with pmount, you can use labels and uuids as described in fstab (5) for devices present in /etc/fstab. In this case, the device name need to match exactly the corresponding entry in /etc/fstab, including the LABEL= or UUID= part. Important note for Debian: The permission to execute pumount is restricted to members of the system group plugdev. Please add all desktop users who shall be able to use pmount to this group by executing adduser user plugdev (as root). OPTIONS
-l, --lazy Lazy unmount. Detach the filesystem from the filesystem hierarchy now, and cleanup all references to the filesystem as soon as it is not busy anymore. (Requires kernel 2.4.11 or later.) IMPORTANT NOTES This option should not be used unless you really know what you are doing, as chances are high that it will result in data loss on the removable drive. Please run pumount manually and wait until it finishes. In addition, pumount will not luksClose a device which was unmounted lazily. --luks-force Normally, pumount will not luksClose (see cryptsetup(1)) a device pmount did not open. However, you can bypass this restriction with this flag. You probably will need it if you did mess around with the /var/lock/pmount_luks directory. -h, --help Print a help message and exit successfully. -d, --debug Enable verbose debug messages. --version Print the current version number and exit successfully. POLICY
The umount will succeed if all of the following conditions are met: o device is a block device in /dev/ (it does not need to exist if -l is supplied) o device is not in /etc/fstab (if it is, pmount executes umount device as the calling user to handle this transparently) o device is mounted according to /etc/mtab and /proc/mounts with the calling user's uid o mount point is in /media PUMOUNT AND MISSING DEVICES
pumount now supports unmounting devices that have gone missing for some reason, such as a brutal removal of the device, or a kernel/hard- ware problem. Just specify the mount point as argument for pumount. SEE ALSO
pmount(1), cryptsetup(1), umount(8) AUTHOR
pmount is developed by Martin Pitt <martin.pitt@canonical.com>. Martin Pitt August 27, 2004 pumount(1)
Man Page

Featured Tech Videos