Hi kp,

On Tue, 2010-10-26 at 16:38 +0200, KP Kirchdoerfer wrote:
> Am Montag, 25. Oktober 2010, 22:39:53 schrieb davidMbrooke:
> > Hi,

> > 
> > In summary, the output from "/var/lib/shorewall/.start version" is being
> > seen as "Processing /etc/shorewall/params ...<CR>4.4.13.1" rather than
> > simply "4.4.13.1". The "Processing ..." message is being generated by
> > function progress_message2() in /var/lib/shorewall/.start
> 
> A plain lrp starts without errors.
Not for me. If I delete configdb.lrp and reboot I still get the same
error.
> 
> What's the content of /etc/shorewall/param?
No change from the standard file.
> 
If nobody can reproduce this error it may be something else I have done
wrong, or a quirk of my hardware setup or my package choices. Let's
proceed to build Beta #1 and see what the other testers find.
> 
> > 
> > A possibly related problem is the contents of /var/log/shorewall.log:
> >     Oct 25 19:23:42 Compiling iptables-restore input for chain
> > mangle:...
> >     Oct 25 19:23:42 Shorewall configuration compiled
> > to /var/lib/shorewall/.start
> >     Oct %_d 19:23:42 Processing /etc/shorewall/params ...
> >     Oct %_d 19:23:42 Processing /etc/shorewall/params ...
<snip>
> Tom already sent me a patch, which I haven't applied yet. It's caused by bb 
> regression in date (an older bb version worked, newer ones fail).
OK. If the two problems are not connected this is trivial, maybe not
even worth fixing...
>  
> kp



------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to