Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ivmconfigconditions.xml(5) [suse 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)

Check Out this Related Man Page

IPTABLES-XML(1) 						  iptables 1.4.21						   IPTABLES-XML(1)

NAME

       iptables-xml -- Convert iptables-save format to XML

SYNOPSIS

       iptables-xml [-c] [-v]

DESCRIPTION

       iptables-xml  is  used  to convert the output of iptables-save into an easily manipulatable XML format to STDOUT.  Use I/O-redirection pro-
       vided by your shell to write to a file.

       -c, --combine
	      combine consecutive rules with the same matches but different targets. iptables does not currently support more than one target  per
	      match,  so this simulates that by collecting the targets from consecutive iptables rules into one action tag, but only when the rule
	      matches are identical. Terminating actions like RETURN, DROP, ACCEPT and QUEUE are not combined with subsequent targets.

       -v, --verbose
	      Output xml comments containing the iptables line from which the XML is derived

       iptables-xml does a mechanistic conversion to a very expressive xml format; the only semantic considerations are for -g and -j  targets	in
       order to discriminate between <call> <goto> and <nane-of-target> as it helps xml processing scripts if they can tell the difference between
       a target like SNAT and another chain.

       Some sample output is:

       <iptables-rules>
	 <table name="mangle">
	   <chain name="PREROUTING" policy="ACCEPT" packet-count="63436" byte-count="7137573">
	     <rule>
	      <conditions>
	       <match>
		 <p>tcp</p>
	       </match>
	       <tcp>
		 <sport>8443</sport>
	       </tcp>
	      </conditions>
	      <actions>
	       <call>
		 <check_ip/>
	       </call>
	       <ACCEPT/>
	      </actions>
	     </rule>
	   </chain>
	 </table> </iptables-rules>

       Conversion from XML to iptables-save format may be done using the iptables.xslt script and xsltproc, or a custom program using  libxsltproc
       or similar; in this fashion:

       xsltproc iptables.xslt my-iptables.xml | iptables-restore

BUGS

       None known as of iptables-1.3.7 release

AUTHOR

       Sam Liddicott <azez@ufomechanic.net>

SEE ALSO

       iptables-save(8), iptables-restore(8), iptables(8)

iptables 1.4.21 														   IPTABLES-XML(1)
Man Page