One way of solving this is for your "BeforeHostUp" script to create a temp file, like "/tmp/norun.tmp". Then in your "HostUp" script, you check if the "/tmp/norun.tmp" file exists, and exit if it does.
That way, the first time HostUp event fires, your script will not run. After the instance reboots, it will clear out the "/tmp" dir and therefor, your HostUp script will not find the temp-file and therefor run. Regards, Daniele On Wednesday, April 8, 2015 at 1:11:17 PM UTC-7, Eugene wrote: > > I'm a new Scalr user, so please forgive me if this is a dumb question. > > I'm doing a bunch of initialization steps in BeforeHostUp. The last step > is a reboot of the instance. Of course, as soon as the reboot script runs, > it exits 0 and HostUp event fires. However, the instance is going into > reboot, so I'd like to wait until it finishes booting, otherwise it's added > to load balancers in an unhealthy state. > > What's the bay way to accomplish this? > > thanks! > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" 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/d/optout.
