more Config.OS EEXTRA=-DSOLARIS -DHIGHFIRST IEXTRA=-lsocket -lnsl -lresolv TEXTRA=-lpthread EEXTRA=-DSOLARIS -DHIGHFIRST IEXTRA=-lsocket -lnsl -lresolv TEXTRA=-lpthread EEXTRA=-DSOLARIS -DHIGHFIRST IEXTRA=-lsocket -lnsl -lresolv TEXTRA=-lpthread EEXTRA=-DSOLARIS -DHIGHFIRST IEXTRA=-lsocket -lnsl -lresolv TEXTRA=-lpthread EEXTRA=-DSOLARIS -DHIGHFIRST IEXTRA=-lsocket -lnsl -lresolv TEXTRA=-lpthread CEXTRA=-DCLIENT CEXTRA=-DLOCAL EEXTRA=-DSOLARIS -DHIGHFIRST IEXTRA=-lsocket -lnsl -lresolv TEXTRA=-lpthread EEXTRA=-DSOLARIS -DHIGHFIRST IEXTRA=-lsocket -lnsl -lresolv TEXTRA=-lpthread
On Fri, Feb 1, 2013 at 12:42 AM, Jb Cheng <[email protected]> wrote: > Could you post the content of Config.OS after you run 'make all'? > > On Thursday, January 31, 2013 10:43:32 AM UTC-8, brownwrap wrote: > >> Well, actually it is on a secured net, so I can't give you access. >> >> On Thu, Jan 31, 2013 at 11:39 AM, dan (ddp) <[email protected]> wrote: >> >>> On Thu, Jan 31, 2013 at 1:34 PM, Greg Ramos <[email protected]> wrote: >>> > I guess what I don't understand you when you say fixing my shell or the >>> > shell script. I was able to run the install.sh on CentOS without a >>> hitch. >>> > Bottom line is, it doesn't seem to be working on Solaris, though >>> someone >>> > said they did install it under Sol 10. I >>> > >>> >>> Yep, either Solaris's shell is horrible trash that does not seem to be >>> able to handle a fairly basic shell script, or there is something >>> wrong with the shell script that only shows up under Solaris. I don't >>> have access to Solaris. There isn't a lot I can do. In the past the >>> solaris admins I've worked with didn't mind doing some work to get >>> things working, which is why I suggested getting a better shell or >>> trying to get the install script working. >>> >>> You can always give me access to your Solaris system. I'd need an >>> account I can ssh into and root access. >>> >>> > On Thu, Jan 31, 2013 at 11:24 AM, dan (ddp) <[email protected]> wrote: >>> >>> >> >>> >> On Thu, Jan 31, 2013 at 1:17 PM, Greg Ramos <[email protected]> >>> wrote: >>> >> > Some of them exist, but they aren't in any bin directory: >>> >> > >>> >> >>> >> So.... No, they don't exist. >>> >> >>> >> It really seems like fixing your shell would be the easiest way to >>> >> solve this. Or even trying to debug the shell script... >>> >> >>> >> > file src/addagent/manage_agents >>> >> > src/addagent/manage_agents: ELF 32-bit MSB executable SPARC >>> Version >>> >> > 1, >>> >> > dynamically linked, not stripped >>> >> > >>> >> > >>> >> > >>> >> > On Thu, Jan 31, 2013 at 11:04 AM, dan (ddp) <[email protected]> >>> wrote: >>> >> >> >>> >> >> On Thu, Jan 31, 2013 at 1:02 PM, Greg Ramos <[email protected]> >>> >>> >> >> wrote: >>> >> >> > Well, I did not make any directory other than /var/ossec. Make >>> all >>> >> >> > created >>> >> >> > all of the sub-directories and what's in them. >>> >> >> > >>> >> >> > >>> >> >> > On Thu, Jan 31, 2013 at 10:17 AM, dan (ddp) <[email protected]> >>> wrote: >>> >> >> >> >>> >> >> >> On Thu, Jan 31, 2013 at 12:01 PM, Greg Ramos <[email protected] >>> > >>> >>> >> >> >> wrote: >>> >> >> >> > I did the make all in the src directory without any errors, >>> but >>> >> >> >> > the >>> >> >> >> > bin >>> >> >> >> > directory is pretty empty: >>> >> >> >> > >>> >> >> >> > ls -larth /var/ossec/bin >>> >> >> >> > total 30 >>> >> >> >> > -r-xr-x--- 1 root ossec 4.3K Jan 26 01:46 util.sh >>> >> >> >> > -r-xr-x--- 1 root ossec 7.4K Jan 26 01:46 >>> >> >> >> > ossec-control >>> >> >> >> > dr-xr-x--- 14 root ossec 512 Jan 30 10:18 .. >>> >> >> >> > dr-xr-x--- 2 root ossec 512 Jan 30 10:18 . >>> >> >> >> > >>> >> >> >> >>> >> >> >> I don't think make all installs anything, just builds the >>> binaries. >>> >> >> >> >>> >> >> >> > >>> >> >> >> > If I do any other make I get this error: >>> >> >> >> > >>> >> >> >> > make server >>> >> >> >> > cp: cannot access ../bin/ossec* >>> >> >> >> > cp: cannot access ../bin/manage_agents >>> >> >> >> > cp: cannot access ../bin/syscheck_update >>> >> >> >> > cp: cannot access ../bin/verify-agent-conf >>> >> >> >> > cp: cannot access ../bin/clear_stats >>> >> >> >> > cp: cannot access ../bin/list_agents >>> >> >> >> > cp: cannot access ../bin/agent_control >>> >> >> >> > cp: cannot access ../bin/syscheck_control >>> >> >> >> > cp: cannot access ../bin/rootcheck_control >>> >> >> >> > >>> >> >> >>> >> >> Do these files exist? >>> >> >> >>> >> >> >> >>> >> >> >> I'm guessing those files don't exist? >>> >> >> >> >>> >> >> >> You're probably best off finding out what common thing the >>> Solaris >>> >> >> >> /bin/sh can't handle, or install a shell that handles shell >>> code, >>> >> >> >> like >>> >> >> >> bash. >>> >> >> >> >>> >> >> >> It's possible that changing: >>> >> >> >> if [ "`isUpdate`" = "${TRUE}" -a "x${USER_CLEANINSTALL}" = "x" >>> ]; >>> >> >> >> then >>> >> >> >> >>> >> >> >> to >>> >> >> >> >>> >> >> >> if [ "`isUpdate`" = "${TRUE}" -a x"${USER_CLEANINSTALL}" = "x" >>> ]; >>> >> >> >> then >>> >> >> >> >>> >> >> >> might make a difference. I'm not sure why it should matter, but >>> >> >> >> every >>> >> >> >> other system handles install.sh fine (except for maybe crippled >>> >> >> >> Linuxes running dash). >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > On Thu, Jan 31, 2013 at 9:05 AM, Greg Ramos < >>> [email protected]> >>> >>> >> >> >> > wrote: >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> OK, I did as you requested. There was a lot more output, but >>> here >>> >> >> >> >> is >>> >> >> >> >> where >>> >> >> >> >> it dies: >>> >> >> >> >> >>> >> >> >> >> + echo -- Press ENTER to continue or Ctrl-C to abort. -- >>> >> >> >> >> >>> >> >> >> >> -- Press ENTER to continue or Ctrl-C to abort. -- >>> >> >> >> >> + [ X = X ] >>> >> >> >> >> + read ANY >>> >> >> >> >> >>> >> >> >> >> + . ./src/init/update.sh >>> >> >> >> >> >>> >> >> >> >> ./install.sh: syntax error at line 142: `$' unexpected >>> >> >> >> >> >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > -- >>> >> >> >> > >>> >> >> >> > --- >>> >> >> >> > You received this message because you are subscribed to the >>> Google >>> >> >> >> > Groups >>> >> >> >> > "ossec-list" group. >>> >> >> >> > To unsubscribe from this group and stop receiving emails from >>> it, >>> >> >> >> > send >>> >> >> >> > an >>> >> >> >> > email to ossec-list+...@**googlegroups.com. >>> >>> >> >> >> > For more options, visit https://groups.google.com/** >>> groups/opt_out <https://groups.google.com/groups/opt_out>. >>> >> >> >> > >>> >> >> >> > >>> >> >> >> >>> >> >> >> -- >>> >> >> >> >>> >> >> >> --- >>> >> >> >> You received this message because you are subscribed to the >>> Google >>> >> >> >> Groups >>> >> >> >> "ossec-list" group. >>> >> >> >> To unsubscribe from this group and stop receiving emails from >>> it, >>> >> >> >> send >>> >> >> >> an >>> >> >> >> email to ossec-list+...@**googlegroups.com. >>> >>> >> >> >> For more options, visit https://groups.google.com/** >>> groups/opt_out <https://groups.google.com/groups/opt_out>. >>> >> >> >> >>> >> >> >> >>> >> >> > >>> >> >> > -- >>> >> >> > >>> >> >> > --- >>> >> >> > You received this message because you are subscribed to the >>> Google >>> >> >> > Groups >>> >> >> > "ossec-list" group. >>> >> >> > To unsubscribe from this group and stop receiving emails from it, >>> >> >> > send >>> >> >> > an >>> >> >> > email to ossec-list+...@**googlegroups.com. >>> >>> >> >> > For more options, visit https://groups.google.com/** >>> groups/opt_out <https://groups.google.com/groups/opt_out>. >>> >> >> > >>> >> >> > >>> >> >> >>> >> >> -- >>> >> >> >>> >> >> --- >>> >> >> You received this message because you are subscribed to the Google >>> >> >> Groups >>> >> >> "ossec-list" group. >>> >> >> To unsubscribe from this group and stop receiving emails from it, >>> send >>> >> >> an >>> >> >> email to ossec-list+...@**googlegroups.com. >>> >>> >> >> For more options, visit >>> >> >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> >> >>> >> >> >>> >> > >>> >> > -- >>> >> > >>> >> > --- >>> >> > You received this message because you are subscribed to the Google >>> >> > Groups >>> >> > "ossec-list" group. >>> >> > To unsubscribe from this group and stop receiving emails from it, >>> send >>> >> > an >>> >> > email to ossec-list+...@**googlegroups.com. >>> >>> >> > For more options, visit >>> >> > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> > >>> >> > >>> >> >>> >> -- >>> >> >>> >> --- >>> >> You received this message because you are subscribed to the Google >>> Groups >>> >> "ossec-list" group. >>> >> To unsubscribe from this group and stop receiving emails from it, >>> send an >>> >> email to ossec-list+...@**googlegroups.com. >>> >>> >> For more options, visit >>> >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> >>> >> >>> > >>> > -- >>> > >>> > --- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "ossec-list" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an >>> > email to ossec-list+...@**googlegroups.com. >>> >>> > For more options, visit >>> > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> > >>> > >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "ossec-list" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to ossec-list+...@**googlegroups.com. >>> >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "ossec-list" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
