You may be able to change the location in the src/LOCATION file, but I haven't tried it.
On Thu, Nov 10, 2011 at 6:20 AM, alsdks <[email protected]> wrote: > Hello again, > > Thank you dan for the hint. I would imagine this is a ./configure flag > (--prefix=/opt/ossec) , but there is no configure file under src. > My knowledge is limited in this area ,can you help me what would be > the exact command \ procedure ? > > Thank you in advance ! > Cheers > > On Nov 10, 12:16 am, "dan (ddp)" <[email protected]> wrote: >> You have to compile it for the location you want to install it in. You >> can change it to /opt/ossec before compilation. >> >> >> >> >> >> >> >> On Wed, Nov 9, 2011 at 4:10 PM, alsdks <[email protected]> wrote: >> > Hello, >> >> > I was testing binary installations , as described here >> >http://www.ossec.net/doc/manual/installation/installation-binary.html >> > , and run into or a strange situation. When installed the binary to a >> > new target machine if I change the install directory to something >> > different than the original machine were the binary was built ,for >> > example select /opt/ossec instead of /var/ossec , the installation >> > does not work . >> >> > It tries to find and run things under /var/ossec and not /opt/ >> > ossec. >> >> > Trying to run manage agents for instance gives the following error : >> >> > manage_agents(1209): ERROR: Unable to chroot to directory: '/var/ >> > ossec'. >> >> > and trying to run ossec-control : >> >> > ossec-execd(1226): ERROR: Error reading XML file '/var/ossec/etc/ >> > ossec.conf': XMLERR: File '/var/ossec/etc/ossec.conf' not found. (line >> > 0) >> >> > Anyone has run to this issue before ? I guess it is not a big deal >> > installing to /var/ossec but what if there is some restriction (space >> > or policy ) and we cant ? >> >> > Any ideas much appreciated ! >> >> > Thank you !
