extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-08 16:54:10 +01:00
Code Issues Packages Projects Releases Wiki Activity

Describe the parameters passed to the enable and disable extension scripts

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2017-08-04 12:38:14 -07:00
parent 657215f9b5
commit 56c8f70b52
No known key found for this signature in database
GPG Key ID: 96E6B3F2423A4D10
1 changed files with 38 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
docs/shorewall_extension_scripts.xml
View File

@ -611,6 +611,44 @@ cat -</programlisting>
</tgroup>
</informaltable></para>
<para>The contents of each run-time script is placed in a shell
function, so you can declare local variables and can use the
<command>return</command> command. The functions generated from the
<filename>enable</filename> and <filename>disable</filename> scripts are
passed three arguments:</para>
<variablelist>
<varlistentry>
<term>$1</term>
<listitem>
<para>Physical name of the interface that was enabled or
disabled.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>$2</term>
<listitem>
<para>Logical name of the interface.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>$3</term>
<listitem>
<para>Name of the Provider, if any, associated with the
interface.</para>
</listitem>
</varlistentry>
</variablelist>
<para>As described above, the function generated from the
<filename>isusable</filename> script is passed a single argument that
names a network interface.</para>
<para>With the exception of postcompile, compile-time extension scripts
are executed using the Perl 'eval `cat
&lt;<emphasis>file</emphasis>&gt;`' mechanism. Be sure that each script