|
From: Michael O'C. <mi...@ch...> - 2004-07-07 21:31:47
|
Hi Mike S,
> * Are all of these processes identical or are they performing different
> tasks? If the latter, you could probably use a central config file and
> limit the exposure of the changes by assigning different categories to
> different processes.
Hmmm, the procs are a mixture, some of the same, some different...I'd
considered this, but it would prove too cumbersome.
> * Use one central config file, edit it to debug a single process, but
> filter messages at the appender level based on process ID/name, using a
> custom filter:
> log4perl.appender.MyAppender.Filter = sub { $$ == 1234 };
> All other processes would pick up the change via init_and_watch, but
> their messages would be blocked by the filter.
> * Use the signal feature of init_and_watch(). In this case, processes
> won't periodically check the config file for modifications, but wait for
> a predefined signal to be sent to them. This way, you would have to
> trigger the update via an external program, sending the update signal to
> all processes which need to re-init.
These two options sound like the best approach, until support for multiple
config files can be provided. Thanks for your help, and prompt response!!!
Do you have a list of concerns regarding multiple config files? I may be
able to spend some time assisting in providing a solution.
Thanks!
Mike.
|