Done it, and syscheck does not start. Thank you both for your time. Needless to say that to disable a feature one must edit code, its not how it was supposed to work.
On Thu, Apr 9, 2015 at 12:24 PM, Matthias Fraidl <[email protected]> wrote: > On 04/09/2015 01:20 PM, Ricardo Perre wrote: > > Thanks for you reply. > > Can you be more specific? > > What should i remove from that script? Should I read the code and figure > it > > out? > > have a look at the ${ossecdir}/bin/ossec-control script and remove the > ossec-syscheckd from DAEMONS and SDAEMONS definition. > > regards, > matthias > > -- > Matthias Fraidl > > Technical Operations > __________________________________________________ > > nic.at GmbH > Jakob-Haringer-Str. 8/V, 5020 Salzburg, Austria > > Tel: +43 662 46 69-718 > Fax: +43 662 46 69-19 > > E-Mail: mailto:[email protected] > Web: http://www.nic.at > > UID-Nr.: ATU 45305101 > LG Salzburg / FN 172568b > Sitz / location: Salzburg > DVR-Nr.: 0968935 > __________________________________________________ > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "ossec-list" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ossec-list/P6iMIZC7o9I/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Ricardo Perre -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
