On Saturday, February 20, 2016 at 3:43:59 AM UTC+5:30, Ryan Schulze wrote: > > Have you tried setting USER_NO_STOP="y" (we use ansible too for building > the binaries)? > > Yes, the problem was only when running install.sh a second time (this is run via ansible, so the playbook can get run a second time, see https://groups.google.com/forum/#!topic/ossec-list/UBkWpp9T9ec).
When install.sh discovers an existing install it seems to always prompt no matter the USER_NO_STOP value. I had to explicitly set USER_UPDATE=y in that case -- but not in the case of the first install. I also had to set USER_CLEANINSTALL=y to get the seond run to actually make changes to the install. -- --- 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/d/optout.
