On Thu, Dec 27, 2012 at 12:21 PM, Kyle Haefner
<kyle.haef...@colostate.edu> wrote:
> Keep in mind that upgrades tend to replace these files.
> George: Any recommendations for making permanent changes to cf-input files?
if the snmptrapd cf script shuts down and service it didn't start then
it's a bug and we should fix it upstream.
if you drop a new file into
/usr/share/sipxecs/cfinputs/plugin.d/foo.cf
and add
bundle agent foo {
reports:
linux::
"hello world";
}
then sipxecs will not touch it. In this foo.cf script, you have
access to all sorts of variables and flags and can add/override many
things.
We could mark *.cf files as "Configuration" files according to rpm
spec and yum upgrades would not replace them, but I feel that's a
little dangerous. Comments?
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
