On 04/09/2012 09:08 PM, Tom Eastep wrote:
> Thanks, John but this isn't related to the perl-digest-sha1
> dependency. I suspect that the OP installed the RPM which is
> SuSE-specific. -Tom You do not need a parachute to skydive. You only
> need a parachute to skydive twice.
> --
>> I see the following when using 4.5.2 beta version. The config
>> files are in the current directory.
>> # shorewall check .
>> /sbin/shorewall: 47: -: not found
>> Checking...
>> # shorewall start .
>> /sbin/shorewall: 47: -: not found
>> Compiling...
>> Apart from that, normal compilation oc
On 04/10/2012 02:36 AM, Mail Lists wrote:
> O
> I did install per the rpm. This is the same way I have been
> installing shorewall since I can remember.
> What I ended up doing was upgrading to the rc of 4.5.2 and all is fine.
> I would still like to have some idea as to what I was doing w
On 04/10/2012 05:11 AM, Fred Maillou wrote:
>>> I see the following when using 4.5.2 beta version. The config
>>> files are in the current directory.
>
>>> # shorewall check .
>>> /sbin/shorewall: 47: -: not found
>>> Checking...
>
>>> # shorewall start .
>>> /sbin/shorewall: 47: -: not found
>>
The '- not found' has to do with:
elif - -f ${SHOREAWLLRC_HOME}/.shorewallrc;
instead of:
elif [ -f ${SHOREAWLLRC_HOME}/.shorewallrc ];
The .start has also the same syntax.--
Better than sec? Nothing is better tha
> Beta 4 was pretty broken. These problems are not present in RC 2.
OK! Thanks.--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monit
On 04/10/2012 09:49 AM, Tom Eastep wrote:
> On 04/10/2012 02:36 AM, Mail Lists wrote:
>> O
>>I did install per the rpm. This is the same way I have been
>> installing shorewall since I can remember.
>> What I ended up doing was upgrading to the rc of 4.5.2 and all is fine.
>> I would still
The Shorewall Team is pleased to announce the availability of Shorewall
4.5.2.
Package maintainers should note the second Known Problem listed below. A
4.5.2.1 version will be released shortly to work around this limitation.
