You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
frisco 1d1139428b
Branched r1161 trunk for 0.3.5 release
14 years ago
..
README Branched r1161 trunk for 0.3.5 release 14 years ago
_event_scripts_ Branched r1161 trunk for 0.3.5 release 14 years ago
apache2_dav Branched r1161 trunk for 0.3.5 release 14 years ago
samba Branched r1161 trunk for 0.3.5 release 14 years ago

README

Event scripts for CryptoBox events


If you want to execute specific actions according to changes of the cryptobox,
then you can just add your own scripts to this directory.
These scripts are called with root user permissions.

The common synopsis for all event scripts is:
SCRIPTNAME EVENT [[EVENT_INFOS]...]


1) Possible events
Supported events:
premount|postmount|preumount|postumount:
called before and after (u)mounting of a volume
arguments (in this order):
- device: name of the underlying device
- vol_name: name of the (u)mounted volume
- vol_type: type of the volume (plain|luks)
- mount_dir: mountpoint of the volume


2) Preperation of event scripts
Every event script has to fulfill the following conditions:
- be executable (for the cryptobox user and for root)
- be writeable for root only
- its parent directories must be writeable for root only
- the directory of the script must contain a file called '_event_scripts_' (to prevent abuse)


3) Storing settings
If your custom event script needs to write information to a file, then it
should create this file below /var/cache/cryptobox-server/settings/misc/.
(adapt this directory to your setup, if you changed the default settings of
[Locations]->SettingsDir)