Tom Eastep wrote:
> My point is simply that there is a major distribution where /bin/sh
> doesn't support '=='.
I've no problem with that whatsoever. In fact, I wasn't aware at the
time I issued the patch that this construct won't work in Debian as I
already knew it worked on all the shells I ha
On 5/9/13 3:22 PM, "Dash Four" wrote:
>
>
>Tom Eastep wrote:
>> On 5/8/13 5:33 PM, "Dash Four" wrote:
>>
>>> Tom Eastep wrote:
>>>
On 5/7/13 4:30 PM, "Dash Four" wrote:
> Tom Eastep wrote:
>
>> Patch attached.
> Applied and tested with changes (
Tom Eastep wrote:
> Please give this a try (apply on top of earlier patch).
>
Yep, all is in order now. Looking at the changes, I am a bit miffed as
to how was this working for you before.
--
Learn Graph Databases -
Tom Eastep wrote:
> On 5/8/13 5:33 PM, "Dash Four" wrote:
>
>> Tom Eastep wrote:
>>
>>> On 5/7/13 4:30 PM, "Dash Four" wrote:
>>>
Tom Eastep wrote:
> Patch attached.
Applied and tested with changes (see patch attached),
>>> You are aware
On 5/8/13 5:33 PM, "Dash Four" wrote:
>
>Tom Eastep wrote:
>> On 5/7/13 4:30 PM, "Dash Four" wrote:
>>
>>
>>> Tom Eastep wrote:
>>>
Patch attached.
>>> Applied and tested with changes (see patch attached),
>>>
>>
>> You are aware that '==' is only supported
On 5/8/13 5:33 PM, "Dash Four" wrote:
>
>>> but still doesn't
>>> work. When I make modifications to my /etc/shorewall and then execute
>>> "shorewall compile -c" I am always getting "/var/lib/shorewall/firewall
>>> is up to date -- no compilation required", which is clearly wrong. As
>>> far as
Tom Eastep wrote:
> On 5/7/13 4:30 PM, "Dash Four" wrote:
>
>
>> Tom Eastep wrote:
>>
>>> Patch attached.
>>>
>>>
>> Applied and tested with changes (see patch attached),
>>
>
> You are aware that '==' is only supported by bash and that much of the
> world outside of Redhat
On Wed, May 8, 2013 at 4:23 AM, Simon Matter wrote:
> Thanks for your contribution but for two reasons I prefer the openvpn patch:
>
> 1) What you suggest doesn't work if openvpn restarts a tunnel itself
> without the openvpn process being stopped and restarted by somehing
> outside of openvpn.
We
>> I don't know your exact requirements but in my situation I needed
>> openvpn
>> being able to run scripts before tun/tap is opened, not after. That's
>> not
>> possible with current openvpn versions and one has to hack around in
>> the
>> init script or other facilities like firewall.
> One othe
On Wed, 2013-05-08 at 08:42 +0200, Simon Matter wrote:
>
> Hi,
Hey,
>
> This is a bit OT because it more touches openvpn than shorewall,
> but...
To jump on this bandwagon a bit...
>
> I don't know your exact requirements but in my situation I needed
> openvpn
> being able to run scripts befor
>
> Tom Eastep wrote:
>> Patch attached.
>>
> Applied and tested with changes (see patch attached), but still doesn't
> work. When I make modifications to my /etc/shorewall and then execute
> "shorewall compile -c" I am always getting "/var/lib/shorewall/firewall
> is up to date -- no compilation r
On 5/7/13 4:30 PM, "Dash Four" wrote:
>
>Tom Eastep wrote:
>> Patch attached.
>>
>Applied and tested with changes (see patch attached),
You are aware that '==' is only supported by bash and that much of the
world outside of Redhat doesn't use bash as /bin/sh? I'm guessing not.
I will never a
Tom Eastep wrote:
Patch attached.
Applied and tested with changes (see patch attached), but still doesn't
work. When I make modifications to my /etc/shorewall and then execute
"shorewall compile -c" I am always getting "/var/lib/shorewall/firewall
is up to date -- no compilation required",
On 05/06/2013 03:57 PM, Dash Four wrote:
>
>
> Tom Eastep wrote:
>
>>
>> What I'm suggesting is to replace all of that with:
>>
>> if [ $PRODUCT == shorewall -o $PRODUCT == shoreawll6 ]; then
>> ${SBINDIR}/$PRODUCT compile -c
>> fi
>>
>> 'compile -c' will compile ${VARDIR}/${PRODUCT}/firewall
Tom Eastep wrote:
> On 05/06/2013 11:22 AM, Dash Four wrote:
>
>> Tom Eastep wrote:
>>
I see your point and is a good one.
Perhaps another alternative could be implemented since the problem
arises only on reboot. Currently, I have shorewall-init as a service
dis
On 5/6/13 2:18 PM, "Tom Eastep" wrote:
>On 05/06/2013 11:22 AM, Dash Four wrote:
>>
>> Tom Eastep wrote:
I see your point and is a good one.
Perhaps another alternative could be implemented since the problem
arises only on reboot. Currently, I have shorewall-init as a service
On 05/06/2013 11:22 AM, Dash Four wrote:
>
> Tom Eastep wrote:
>>> I see your point and is a good one.
>>>
>>> Perhaps another alternative could be implemented since the problem
>>> arises only on reboot. Currently, I have shorewall-init as a service
>>> disabled, simply because ifupdown-local u
Tom Eastep wrote:
>> I see your point and is a good one.
>>
>> Perhaps another alternative could be implemented since the problem
>> arises only on reboot. Currently, I have shorewall-init as a service
>> disabled, simply because ifupdown-local usually takes care of
>> everything. However, if y
On 05/06/2013 10:15 AM, Dash Four wrote:
>
> Tom Eastep wrote:
>> On 05/05/2013 10:17 AM, Dash Four wrote:
>>
>>> I've decided to make a clean break as the AUTOMAKE thread was getting a
>>> bit off-topic. These are my findings so far:
>>>
>>> 1. During boot, when the OS is bringing my loopback
Tom Eastep wrote:
> On 05/05/2013 10:17 AM, Dash Four wrote:
>
>> I've decided to make a clean break as the AUTOMAKE thread was getting a
>> bit off-topic. These are my findings so far:
>>
>> 1. During boot, when the OS is bringing my loopback interface up I am
>> getting the following messages
On 05/05/2013 10:17 AM, Dash Four wrote:
> I've decided to make a clean break as the AUTOMAKE thread was getting a
> bit off-topic. These are my findings so far:
>
> 1. During boot, when the OS is bringing my loopback interface up I am
> getting the following messages:
>
> Bringing up loopback in
I've decided to make a clean break as the AUTOMAKE thread was getting a
bit off-topic. These are my findings so far:
1. During boot, when the OS is bringing my loopback interface up I am
getting the following messages:
Bringing up loopback interface: SIOCADDRT: Network is unreachable
SIOCADD
22 matches
Mail list logo
