Then restart scalr-upd-client daemon On Friday, June 1, 2012 5:27:08 PM UTC+3, Marat wrote: > > You can set repository = latest in /etc/scalr/updclient.ini to force using > latest repo until new Scalr OS release with controlling interface will be > published. > > On Friday, June 1, 2012 5:16:02 PM UTC+3, Val wrote: >> >> I am assuming the update doesn't happend automagically because on RHEL >> OSes the scalr-latest.repo is not enabled. I had to enable it and perform >> the update. The Scalr folks need to put the fix in the scalr-delay.repo in >> order for the automatic update to occur. At least, that has been my >> experience. >> >> On Friday, June 1, 2012 5:54:02 AM UTC-7, Dale-Kurt Murray wrote: >>> >>> Marat, How do we update to the latest version? Does the update happen on >>> rebooting the instance or by rebuilding the role? >>> >>
-- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/scalr-discuss/-/n_RKn98O0ywJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en.
