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

IVMCONFIGCONDITIONS.XML(5)					File Formats Manual					IVMCONFIGCONDITIONS.XML(5)

NAME
IvmConfigConditions.xml - rules for processing hardware conditions by ivman(8) DESCRIPTION
IvmConfigConditions.xml specifies hardware conditions to be caught by ivman(8), and allows running of certain commands when devices emit conditions. IvmConfigConditions.xml is parsed as an XML file. The general form of the file is: <?xml version="1.0" encoding="UTF-8"?> <ivm:ConditionsConfig version="0.1" xmlns:ivm="http://www.eikke.com/ivm"> <ivm:Match name="matchname" value="matchvalue"> <ivm:Condition name="conditionname1" exec="command1" /> <ivm:Condition name="conditionname1" exec="command1" /> </ivm:Match> ... </ivm:PropertiesConfig> Each time a condition is emitted by a device, this file will be parsed. If the Match rule matches the device on which the condition came from, and the Condition rule matches the name of the condition which occurred, then the command specified in the 'exec' option will be exe- cuted. A Match element can have any of the following names: ivm.mountable Whether or not HAL specifies that a device can and should be mounted. Must be "true" or "false". hal.anything The string in place of "anything" will be taken as the name of a HAL property string for the device, and the value of the prop- erty will be compared to the value given. Run 'lshal' to see a list of HAL properties which can be used here. * Match every device. Use with care! As many Matches can be nested as is desired. Condition names usually take the form of something like 'ButtonPressed', which may occur when an ACPI-enabled button is pressed on your machine. See the HAL specification for a full list of possible conditions. The exec attributes of Condition tags support substitution of HAL device properties. This is accomplished by surrounding the property name with $ symbols. For instance, if $hal.volume.mount_point$ is within a command, it will be replaced with the volume's mount point before execution. No character escaping is done in the substitution, but the characters ' and " are replaced with ?, so you can surround the sub- stitution with quotes without fear. Remember that this is an XML file, which means that characters which have a special meaning in XML (entities) need to be escaped. Some characters which are popular in shell scripting (&, <, >) are among these special characters. As a quick reference, & becomes &amp; , < becomes &lt; , > becomes &gt; , ' becomes &apos; and " becomes &quot; . SEE ALSO
ivman(8), IvmConfigBase.xml(5), IvmConfigActions.xml(5) 12 May 2005 IVMCONFIGCONDITIONS.XML(5)
Man Page