https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-713 Instrument control development <p>In order for <tt>ics_launch</tt> to be useful for a full system boot, various actors will need to wait for the tron hub to come up. Wrap that.</p> <p>And in a few cases (and actually just for convenience), it will be useful to wait until some actor is running before launching something.</p> <p>Both cases can I think be handled with minor adaptations of <tt>oneCmd.py hub actors</tt>. That, unfortunately, depends on <tt>tron_actorcore</tt>, so purity will have to be set aside.</p> INSTRM-713

Add wait-for-tron and wait-for-actor scripts

Task Normal Open Unresolved cloomis cloomis SPS Subaru Wed, 17 Jul 2019 14:34:45 +0000 Tue, 6 Jul 2021 12:27:56 +0000 ics_launch 0 1 <p>And maybe a <tt>waitForDatabase</tt> before we start the archiver or even tron. Am a little worried about that: yes, the archiver database is important, but its absence should not stop MHS (operations!) from starting after some big mess.</p> <p>Bump. The connection to tron itself is not controlled by the time limit, grr, but something based on the following should work:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>alive=0 while [ ! $alive ]; do nc -z mhs-ics 9877 alive=$? done running=0 while [ ! $running ]; do oneCmd.py --timeLim=5 hub actors running=$? done </pre> </div></div> Development Rank 0|zy0008: Story Points 1.0