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-50 Instrument control development <p>This issue was initially filed into JIRA by 'arnaud.lefur' at 11/Jan/16 1:32 PM.</p> <p>xcuActor does not automatically start when the BEE boots.<br/> I don't what happened, it was the case before</p> INSTRM-50

[xcuActor] xcuActor not starting on BEE booting

Task Major Won't Fix Won't Fix cloomis arnaud.lefur Tue, 27 Dec 2016 00:47:58 +0000 Tue, 29 May 2018 21:07:21 +0000 Tue, 29 May 2018 21:07:21 +0000 0 3 <p>For the <em>bee-r1</em>, I think that's working and could be considered as done, but I have to check I will pay attention next time.</p> <p>For the bee-r2, It's not the case, there is no <b>/etc/rc.local</b>. <br/> But since we considered that dewar as a r0 for thermal test and not a r2. Your startBee.sh script would not have worked anyway.<br/> Either we create a startBee-r0.sh script or we keep doing it manually what do you think <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=fmadec" class="user-hover" rel="fmadec">fmadec</a> ?</p> <p>don't know....</p> <p>either we could do that.<br/> either we could change the dnsmasq according: change r2 into r0</p> <p>My concern is also that we need to track which component was/is use with which CU, meaning that r0 will become r2 at some point. but the track should be done with serial number ...</p> <p>Problem described is now out-of-date. Resolving as won't fix.</p> Development Rank 0|ii01db: