Try "-u local" -u local Update syscheck database locally. I'm not getting a segfault for local or remote clients. Not even clients that aren't connected.
dan On Tue, Mar 24, 2009 at 7:09 PM, matthias platzer <[email protected]> wrote: > > hi, > > I just upgraded to 2.0... > same here, seg fault with local and agent id > ./syscheck_control -i 006 > > Integrity changes for agent 'wsus (006) - x.x.x.x': > Segmentation fault > > immediately after issuing > ./syscheck_update -u 006 > the seg fault is gone for the agent 006. > > But ./syscheck_update -u 000 > > ** Invalid agent id '000' > > How could I update for the local server 000 ? > > Anyway, from ./syscheck_control -h > "-u <id> Updates (clear) the database for the agent." > > Does this mean, clear the database and build a new one or just update > it by running syscheck. And what for is syscheck_update then? > And what would be the proper way to run syscheck on an agent (from the > server) ? > > BTW, I might have found a bug: > On a Windows 2000 Server, agent-2.0, setting syscheck.sleep_after=150 > in internal_options.conf prevents the agent from startup. > > tia+regards, > matthias > > >
