On Thu, Jan 31, 2013 at 1:17 PM, Greg Ramos <brownw...@gmail.com> 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) <ddp...@gmail.com> wrote:
>>
>> On Thu, Jan 31, 2013 at 1:02 PM, Greg Ramos <brownw...@gmail.com> 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) <ddp...@gmail.com> wrote:
>> >>
>> >> On Thu, Jan 31, 2013 at 12:01 PM, Greg Ramos <brownw...@gmail.com>
>> >> 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 <brownw...@gmail.com>
>> >> > 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+unsubscr...@googlegroups.com.
>> >> > 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 ossec-list+unsubscr...@googlegroups.com.
>> >> 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 ossec-list+unsubscr...@googlegroups.com.
>> > 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 ossec-list+unsubscr...@googlegroups.com.
>> 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 ossec-list+unsubscr...@googlegroups.com.
> 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 ossec-list+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
