IVMAN-LAUNCH(8) System Manager's Manual IVMAN-LAUNCH(8)NAME
ivman-launch - launch script for Ivman
SYNOPSIS
ivman-launch [ --exit-with-session <cmd> ] [ OPTIONS ] [ COMMAND [ ARGS... ]]
DESCRIPTION
ivman-launch is a simple script used to launch Ivman. Its sole purpose is to ensure Ivman is closed at the end of a user's login session.
You can use it if your session manager does not properly close Ivman when you log out.
ivman-launch supports the same command-line options as Ivman, and one additional option: --exit-with-session. Thus, there is no point
using ivman-launch if you do not need to use this option.
If you supply a COMMAND (with optional ARGS), the the specified command will be run after ivman is started, and ivman will be killed after
that command exits.
OPTIONS --exit-with-session <cmd>
ivman-launch will block until the command 'cmd' terminates, at which point it will kill Ivman and exit itself. If the command 'cmd'
is not running when ivman-launch is started, Ivman will exit immediately. Note that this option implies Ivman will be called with
the '--nofork' option. option.
--debug --nofork --system
These flags be passed to the launched ivman command.
EXAMPLES
ivman-launch --exit-with-session xinit &
The ivman process will be started, then the xinit process is watched. When the xinit process exits, ivman is killed. Placing this
command in an ~/.xinitrc file would cause Ivman to launch in the background when your session begins, and exit when your session
ends:
ivman-launch /usr/bin/x-window-manager
The ivman process is launched, then /usr/bin/x-window-manager is run, when x-window-manager exits, ivman is killed. This is an
example of how ivman might be launched from Xsession in order to chain several programs together in one session.
SEE ALSO ivman(8)Xsession(5)CREDITS
This script was written by Daniele Favara.
10 February 2006 IVMAN-LAUNCH(8)
Check Out this Related Man Page
IVMCONFIGBASE.XML(5) File Formats Manual IVMCONFIGBASE.XML(5)NAME
IvmConfigBase.xml - options affecting the running of ivman(8)DESCRIPTION
IvmConfigBase.xml contains a few options which affect the behaviour of ivman(8).
IvmConfigBase.xml is parsed as an XML file during Ivman's initialisation. The general form of the file is:
<?xml version="1.0" encoding="UTF-8"?>
<ivm:BaseConfig version="0.2" xmlns:ivm="http://www.eikke.com/ivm">
<ivm:Option name="optionname1" value="optionvalue1" />
<ivm:Option name="optionname2" value="optionvalue2" />
...
</ivm:BaseConfig>
An Option element can have any of the following names:
fork Whether or not Ivman should daemonize itself (run in the background). Must be "true" or "false". In general, for an instance
of Ivman running as root, you want this to be true, but for an instance of Ivman running as non-root, you want this to be false
so the program will close when the user's session ends.
debug Whether or not Ivman should output extra debug information. Must be "true" or "false". If Ivman is running in the background,
debug messages will go to the system log; otherwise, messages will go to stdout(3).
sleep By default, a system-wide instance of Ivman will wait a short while before mounting any device. This is to give a user-mode
instance of Ivman, or another volume manager, a change to mount the volume first, since the system-wide instance of Ivman gen-
erally has more restrictive permissions set on its mounted volumes. If you want to disable this behaviour, set sleep to
"false".
user User account under which Ivman should run. It is suggested that you create an unprivileged user named 'ivman', and add any
commands which need root privileges to ivman's entry in /etc/sudoers . Note that Ivman should still be started as root when
this option is used; it will automatically drop privileges after initialising.
group Group under which Ivman should run. This should be whatever group is required on your system in order to use the 'pmount' com-
mand. Also, if you have a system-wide and not a per-user instance of Ivman running when a mountable device is inserted, the
device will be mounted writeable by users of this group. Note that Ivman should still be started as root when this option is
used; it will automatically drop privileges after initialising.
mountcommand
Command to execute to mount devices. It is recommended you leave this blank, in which case Ivman will automatically detect the
best method of mounting. Specifically, Ivman tries to use (in the following order): pmount-hal(1), pmount(1), mount(8). If
you specify this option, you must also specify umountcommand.
umountcommand
Command to execute to unmount devices. It is recommended you leave this blank. If you specify this option, you must also spec-
ify mountcommand.
umask If neither of mountcommand or umountcommand are specified, and Ivman is running as a system-wide instance, and pmount was
detected, then volumes will be mounted using this umask. When not using pmount, umask should be set in fstab(5), or set in HAL
policy files if fstab-sync is being used. If ommitted, defaults to 022 (rwxr-xr-x).
mountcommand and umountcommand support (and, in most cases, will require) substitution of HAL device properties. This is accomplished by
surrounding the property name with $ symbols. For instance, to use the traditional mount(8) utility for mounting, you would set mountcom-
mand to "mount the characters ' and " are replaced with ?, so you can surround the substitution 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 & , <
becomes < , > becomes > , ' becomes ' and " becomes " .
SEE ALSO ivman(8), IvmConfigActions.xml(5), IvmConfigConditions.xml(5)IvmConfigProperties.xml(5)
6 November 2005 IVMCONFIGBASE.XML(5)