yep... it would be via install.sh
On Tue, Nov 9, 2010 at 11:16 AM, dan (ddp) wrote:
> Your plan is to run the install.sh to re-install, right? I think
> that'd be about the only way it would work.
>
> But I think it should work. Make sure to pay attention to ownership
> and permissions with the
Your plan is to run the install.sh to re-install, right? I think
that'd be about the only way it would work.
But I think it should work. Make sure to pay attention to ownership
and permissions with the files you copy over.
On Tue, Nov 9, 2010 at 1:02 PM, jplee3 wrote:
> Hey guys,
>
> Would I be
On Tue, Nov 9, 2010 at 11:33 AM, Winpy wrote:
> I have replaced my original server and installed the new 2.5.1
> software.
> I have updated all of my Agents to the new version also.
>
> One of the problems that I have always had is that I receive emails
> for all alert levels even though the defau
Hey guys,
Would I be able to move my OSSEC installation to a different folder
path by stopping the current install, reinstalling to a different
path, and then copying the client.keys, decoder.xml, rules, confs, etc
over to the new OSSEC path?
TIA!
I have replaced my original server and installed the new 2.5.1
software.
I have updated all of my Agents to the new version also.
One of the problems that I have always had is that I receive emails
for all alert levels even though the default levels are log level 1
and email alert at 7.
thanks
H
Hi, Just noticed on my 1st installs of the Windows 2.5.1 client on
Server 2008 R2 64bit Enterprise machines... The client doesn't know
what the OS is ...
Name: lcua68
IP: 10.1.100.68
Last keep alive: 2010 Nov 09 08:46:57
OS: Microsoft Windows Unknown (Build 7600) - OSSEC HIDS v2.5.1
any
