From 8318dff8a86fe041b5dd1fc1981783280fb61916 Mon Sep 17 00:00:00 2001 From: teastep Date: Wed, 7 Nov 2007 23:13:08 +0000 Subject: [PATCH] Update Lite documentation for 4.0 git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7626 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- docs/CompiledPrograms.xml | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/docs/CompiledPrograms.xml b/docs/CompiledPrograms.xml index 72cb7f3e3..85c248e63 100644 --- a/docs/CompiledPrograms.xml +++ b/docs/CompiledPrograms.xml @@ -231,18 +231,20 @@ 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 /etc/shorewall/params and /etc/shorewall/shorewall.conf must be readable by all users on the administrative system. Not all packages secure the files that way and you may have to change the file permissions - yourself. /sbin/shorewall uses the SHOREWALL_SHELL setting from - /etc/shorewall/shorewall.conf to determine the - shell to use when compiling programs and it uses the VERBOSITY - setting for determining how much output the compiler generates. All - other settings are taken from the shorewall.conf - file in the remote systems export - directory (see below). + yourself. /sbin/shorewall uses the SHOREWALL_COMPILER setting to + determine which compiler to lanuch. If the compiler is + shorewall-shell, then the SHOREWALL_SHELL setting from + /etc/shorewall/shorewall.conf determines the + shell to use. /sbin/shorewall also uses the VERBOSITY setting for + determining how much output the compiler generates. All other + settings are taken from the shorewall.conf file + in the remote systems export directory (see + below). @@ -883,4 +885,4 @@ CAPVERSION=30405 is the level specified in the shorewall.conf file used when then program was compiled. - + \ No newline at end of file