Hi Cid, thanks for your help and for developing such a great tool. The Cron job might indeed be an option (althought i guess there is no way to be 100% sure the process had enough time to finish all the checks) Does OSSEC always have to run as root? Or will it be sufficient to create a user:group with read access to the target folders? thanks Andreas
Daniel Cid <[EMAIL PROTECTED]> wrote: Hi Andreas, Unfortunately, you can't. Syscheck used to be available as a separate package, but I removed this option a few versions ago because no one was using it. It was only giving us more work, because we always had to make sure that the standalone version was working correctly... You can have a work around that by only enabling syscheck on ossec (and disabling everything else) and having a cron job to start it every night and stopping it 30 minutes later (to give enough time to scan)... Not really what you wanted, but may help. -- Daniel B. Cid dcid ( at ) ossec.net On 11/16/06, Andreas Chatzakis wrote: > Hi all, > I was wondering, > > is syscheck available standalone? I don't need any of the other functions > and syscheck is a great tool and so easy to configure. > > does it always need to run as root? Or can I configure it to run as a > different user? > > And one mroe question. instead of having it running all the time as a > process, could I schedule it or call it from another software and have its > results in the logs or via email? > > thanks in advance > Andreas > > > > ________________________________ > Sponsored Link > > Mortgage rates near 39yr lows. $310,000 Mortgage for $999/mo - Calculate new > house payment --------------------------------- Sponsored Link Degrees for working adults in as fast as 1 year. Bachelors, Masters, Associates. Top schools
