First off, I would like to say thank you for all of the work that has gone in to shorewall. I''ve been using it for years quite happily. I''ve run into a problem though while upgrading to version 3.4.8 running on RHEL5. When I try to start it I get the following errors: /etc/shorewall/params: line 32 MYVAR=1992.168.10.xxx: command not found (I get this error multiple times for all of my variables) My params file looks like this: # ## Server aliases # XXX-BSB="192.168.10.20" XXX-FE="192.168.10.21" XXX-CS="192.168.10.22" (snip) etc. I''ve never seen this before. Does anyone have any idea what would be causing this? Also, the compiler is set to shell, and the params file is exported in shorewall.conf. Kind Regards, Peter Wrangell ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
Peter Wrangell wrote:> First off, I would like to say thank you for all of the work that has > gone in to shorewall. I''ve been using it for years quite happily. > I''ve run into a problem though while upgrading to version 3.4.8 > running on RHEL5. When I try to start it I get the following errors: > > /etc/shorewall/params: line 32 MYVAR=1992.168.10.xxx: command not > found (I get this error multiple times for all of my variables) > > My params file looks like this: > > # > ## Server aliases > # > XXX-BSB="192.168.10.20" > XXX-FE="192.168.10.21" > XXX-CS="192.168.10.22" (snip) etc. > > I''ve never seen this before. Does anyone have any idea what would be > causing this? Also, the compiler is set to shell, and the params file > is exported in shorewall.conf.I''m totally lost. You say that you are upgrading *to* 3.4.8. 3.4.8 was released more that 18 months ago and dropped from support when Shorewall 4.4.0 was released in August of this year. You also mention "the compiler is set to shell" -- Shorewall-perl wasn''t released until 4.0.0 in August of this year. So... a) What version were you running before the upgrade? b) What version are you trying to run now? And, finally, please follow the instructions at http://www.shorewall.net/support.htm#Guidelines when ''shorewall start'' fails. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
My apologies, for taking up your time. I''ll try again running the latest version. I was just confused as to why the params file was not being parsed as a collection of variables. Given enough time I''ll figure it out. Thanks for responding so quickly, and once again sorry for taking up your time. As they say, if everything else fails, take a look at the source. Kind Regards, Peter -----Original Message----- From: Tom Eastep [mailto:teastep@shorewall.net] Sent: Mon 12/14/2009 5:48 PM To: Shorewall Users Subject: Re: [Shorewall-users] params file not being parsed correctly Peter Wrangell wrote:> First off, I would like to say thank you for all of the work that has > gone in to shorewall. I''ve been using it for years quite happily. > I''ve run into a problem though while upgrading to version 3.4.8 > running on RHEL5. When I try to start it I get the following errors: > > /etc/shorewall/params: line 32 MYVAR=1992.168.10.xxx: command not > found (I get this error multiple times for all of my variables) > > My params file looks like this: > > # > ## Server aliases > # > XXX-BSB="192.168.10.20" > XXX-FE="192.168.10.21" > XXX-CS="192.168.10.22" (snip) etc. > > I''ve never seen this before. Does anyone have any idea what would be > causing this? Also, the compiler is set to shell, and the params file > is exported in shorewall.conf.I''m totally lost. You say that you are upgrading *to* 3.4.8. 3.4.8 was released more that 18 months ago and dropped from support when Shorewall 4.4.0 was released in August of this year. You also mention "the compiler is set to shell" -- Shorewall-perl wasn''t released until 4.0.0 in August of this year. So... a) What version were you running before the upgrade? b) What version are you trying to run now? And, finally, please follow the instructions at http://www.shorewall.net/support.htm#Guidelines when ''shorewall start'' fails. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
Peter Wrangell wrote:> My apologies, for taking up your time. I''ll try again running the > latest version. I was just confused as to why the params file was not > being parsed as a collection of variables. Given enough time I''ll > figure it out. Thanks for responding so quickly, and once again sorry > for taking up your time. As they say, if everything else fails, take > a look at the source.No trouble at all -- always glad to help if you continue to have problems with it. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon''s best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
On Mon, Dec 14, 2009 at 04:52:44PM -0800, Peter Wrangell wrote:> /etc/shorewall/params: line 32 MYVAR=1992.168.10.xxx: command not found (I get this error multiple times for all of my variables) > > My params file looks like this:> XXX-BSB="192.168.10.20"> Also, the compiler is set to shellPerhaps because ''-'' isn''t a valid char in a shell variable? Justin ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon''s best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
Justin T Pryzby wrote:> On Mon, Dec 14, 2009 at 04:52:44PM -0800, Peter Wrangell wrote: >> /etc/shorewall/params: line 32 MYVAR=1992.168.10.xxx: command not found (I get this error multiple times for all of my variables) >> >> My params file looks like this: > >> XXX-BSB="192.168.10.20" > >> Also, the compiler is set to shell > > Perhaps because ''-'' isn''t a valid char in a shell variable?Good catch. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon''s best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev