[ossec-list] ossec-.13 agent stopping by itself on CentOS 5 64-bit

2007-10-16 Thread Peter M. Abraham
Greetings: 2007/10/16 09:02:44 ossec-agentd: Started (pid: 7137). 2007/10/16 09:02:44 ossec-agentd: Connecting to server ([ossec server ip]:1514). 2007/10/16 09:02:46 ossec-syscheckd: Started (pid: 7145). 2007/10/16 09:02:46 ossec-rootcheck: Started (pid: 7145). 2007/10/16 09:02:50

[ossec-list] Re: Windows client communication issue

2007-10-16 Thread McClinton, Rick
Anything in the server log? -Original Message- From: ossec-list@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Ry Mills Sent: Monday, October 15, 2007 3:39 PM To: ossec-list@googlegroups.com Subject: [ossec-list] Re: Windows client communication issue Importance: Low

[ossec-list] Re: How are rules enacted?

2007-10-16 Thread Daniel Cid
Hi John, Rick explained it well, just edit your rules at local_rules.xml and restart the server when done. Nothing needs to be restarted at the agent side. As for writing your own rules, the following document can be very helpful: http://www.ossec.net/ossec-docs/auscert-2007-dcid.pdf Thanks,

[ossec-list] Re: ossec-.13 agent stopping by itself on CentOS 5 64-bit

2007-10-16 Thread Daniel Cid
Hi Peter, I have ossec running on 64-bit systems without any problem (both Linux and OpenBSD). Is there any errors on your server log? The following links may help: http://www.ossec.net/wiki/index.php/Errors:AgentCommunication http://www.ossec.net/wiki/index.php/Errors:1403 Btw, if that