SuSeconfig needed or not after changing syslog-ng

Hi,

Because on the OES there are lots of log files and hard to maintain if you have lots of servers we made a connection to a syslog server.

vi /etc/syslog-ng/syslog-ng.conf
destination logserver { tcp("10.10.10.10" port(514)); };
log { source(src); destination(logserver); };

logger test test

I receive the "test" event on our syslog server.

Is Suseconfig needed or not?

Does it harm my OES server by doing the SuseConfig?

Kr,

Joeri
  • jfeyen wrote:

    > Is Suseconfig needed or not?


    Which version of OES are you on? With OES11 or later the configuration
    of syslog-ng is not handled be SuSEconfig any more. You might edit
    /etc/syslog-ng/syslog-ng.conf directly.

    Günther
  • =?UTF-8?B?R8O8bnRoZXIgU2Nod2Fyeg==?=;2414367 wrote:
    jfeyen wrote:

    > Is Suseconfig needed or not?


    Which version of OES are you on? With OES11 or later the configuration
    of syslog-ng is not handled be SuSEconfig any more. You might edit
    /etc/syslog-ng/syslog-ng.conf directly.

    Günther


    Hi Gunther,

    We use OES11SP1 SP2 and OES2015.

    Does it matter that I runned SuSEconfig on those servers?

    Kr,

    Joeri
  • On 17/12/2015 15:56, jfeyen wrote:

    > We use OES11SP1 SP2 and OES2015.
    >
    > Does it matter that I runned SuSEconfig on those servers?


    It shouldn't do as SuSEconfig handles a lot less than it did before. If
    you want to check what SuSEConfig will do on a particular server use
    "SuSEconfig --listmodules".

    HTH.
    --
    Simon
    Micro Focus (Novell/NetIQ) Knowledge Partner

    ------------------------------------------------------------------------
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below. Thanks.
    ------------------------------------------------------------------------