[Firehol-support] link-balancer starting at boot

[Tsaousis, Costa]

Hi Spike.

Nice you like our work.

No particular reason for starting it via cron. Just a preference.
cron will work too.

locking works with all firehol programs. So, only one instance of each will
be running at any given time.
This locking is done with flock, so there are no false positives (the lock
is released even if the programs exits abnormally).

I am running link-balancer for several years now in many sites and distros,
and I never had a hang.

All firehol programs log to syslog. The console output is just informative.
link-balancer also syslogs all changes it does (the commands it runs).

Costa



On Wed, Feb 8, 2017 at 7:04 PM, Spike <spike at drba.org> wrote:

> Dear all,
>
> been running firehol for a little while and it's amazing how well it's
> working and how much it made things simpler for us, really grateful to
> anybody who worked on this.
>
> I'm also using link-balancer and in the docs it explains how you can run it
> at boot:
>
> https://github.com/firehol/firehol/wiki/Link-Balancer#
> running-link-balancer-at-boot
>
> is there any particular reason I'm ignoring why this solution was chosen
> instead of running it from cron say every minute or whatever interval? To
> us that's more robust also in terms of managing the launch of the script
> (fiddling with rc.local and similar always ends up backfiring in my
> experience). Two issues however arise with that:
> - locking, in case the previous execution of link-balancer is hanging for
> whatever reason
> - logging, which would be good to send to syslog
>
> does anybody have any input on this?
>
> thanks,
>
> Spike
> _______________________________________________
> Firehol-support mailing list
> Firehol-support at lists.firehol.org
> http://lists.firehol.org/mailman/listinfo/firehol-support