On 09/16/2014 11:50:56 AM, Thomas King wrote:
> On 16 Sep 2014, at 17:37, Karl O. Pinc <k...@meme.com> wrote:
>
> > On 09/16/2014 04:25:19 AM, Thomas King wrote:
> >
> >> We are thinking about adding features in the following categories:
> >
> >> - Reconfiguration via API: As we want to use pmacct in a dynamic
> >> environment we want to be able to change the configuration via an
> API
> >> without restarting pmacct.
> >
> > Just curious. Why is an API required. Isn't a signal to
> > re-read configs enough?
> If this can be done without interrupting the pmacct operations (and
> losing any data) it is enough
I like the idea of a signal, it being the simplest API there is.
It'd also then be trivial to add support for a system pmacct
startup script that supports a "reload" operation,
without data loss.
Just my 2 cents.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
