Update Lite documentation for 4.0

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7626 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-11-07 23:13:08 +00:00
parent 58d9bfb83a
commit 8318dff8a8

View File

@ -231,18 +231,20 @@
<caution> <caution>
<para>If you want to be able to allow non-root users to manage <para>If you want to be able to allow non-root users to manage
remote filewall systems, then the files remote firewall systems, then the files
<filename>/etc/shorewall/params</filename> and <filename>/etc/shorewall/params</filename> and
<filename>/etc/shorewall/shorewall.conf</filename> must be readable <filename>/etc/shorewall/shorewall.conf</filename> must be readable
by all users on the administrative system. Not all packages secure by all users on the administrative system. Not all packages secure
the files that way and you may have to change the file permissions the files that way and you may have to change the file permissions
yourself. /sbin/shorewall uses the SHOREWALL_SHELL setting from yourself. /sbin/shorewall uses the SHOREWALL_COMPILER setting to
<filename>/etc/shorewall/shorewall.conf</filename> to determine the determine which compiler to lanuch. If the compiler is
shell to use when compiling programs and it uses the VERBOSITY shorewall-shell, then the SHOREWALL_SHELL setting from
setting for determining how much output the compiler generates. All <filename>/etc/shorewall/shorewall.conf</filename> determines the
other settings are taken from the <filename>shorewall.conf shell to use. /sbin/shorewall also uses the VERBOSITY setting for
</filename>file in the remote systems <firstterm>export determining how much output the compiler generates. All other
directory</firstterm> (see below).</para> settings are taken from the <filename>shorewall.conf </filename>file
in the remote systems <firstterm>export directory</firstterm> (see
below).</para>
</caution> </caution>
</listitem> </listitem>