Merge lp:~jml/launchpad/robust-shutdown into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Robert Collins |
Approved revision: | no longer in the source branch. |
Merged at revision: | 11224 |
Proposed branch: | lp:~jml/launchpad/robust-shutdown |
Merge into: | lp:launchpad |
Diff against target: |
14 lines (+1/-3) 1 file modified
lib/devscripts/ec2test/testrunner.py (+1/-3) |
To merge this branch: | bzr merge lp:~jml/launchpad/robust-shutdown |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Collins (community) | Approve | ||
Martin Pool (community) | Approve | ||
Review via email: mp+30888@code.launchpad.net |
Commit message
Timeout ec2 instances using shutdown rather than at.
Description of the change
Follow Martin Pool's recommendations for a more robust timeout on ec2 instances.
----
I observed this message trying to start a remote test run:
ec2test@...$ echo sudo shutdown -h now | at today + 480 minutes
warning: commands will be executed using /bin/sh
job 1 at Sat Jul 24 22:43:00 2010
Can't open /var/run/atd.pid to signal atd. No atd running?
I wonder if this could be responsible for some people seeing their
instances never shut down? It doesn't happen every time. I wonder
too if this could be caused by poking commands into the machine right
after it's started up and therefore before atd is ready to signal
commands? Perhaps we should just run 'sudo -b shutdown -h +480'?
seems plausible to me :-)
(but there are not (yet) any revisions in the mp)