The framebuilder was being flaky. MX_streams would go down, prevent testpoints from working and so forth.
Send Alex up North for a week to fix the code.
Alex came back and installed updates to the frame builder and the mx_streams code (Myrinet Express over Generic Ethernet Hardware) used by the front ends to talk to the frame builder. Instead of 1 stream per model, there's now just 1 per front end handling all communications.
Alex did an SVN update and we now have the latest CDS code.
Self restarting codes:
The frame builder code (daqd) and nds pipe have been added to the fb machine's inittab. Specifically it calls a script called /opt/rtcds/caltech/c1/target/fb/start_daqd.inittab and /opt/rtcds/caltech/c1/target/fb/start_nds.inittab.
The addition to the /etc/inittab file on fb is:
When these codes die they should automatically restart.
Self starting codes at boot up:
The front ends now start the mx_stream script (which lives in /opt/rtcds/caltech/c1/target/fb/ directory) at boot up. They call it with the approriate command line options for that front end. It can be found in the /etc/rc.local file.
They look like: mx_stream -s "c1x02 c1sus c1mcs c1rms" -d fb:0
As always, the front end codes to be started are defined in the /etc/rtsystab file (or on fb, in the /diskless/root/etc/rtsystab file).
However, if it does go down you would need to restart it manually, although it seems more robust now and doesn't seem to go down every time we restart the frame builder.
All the usual front end IOCs and modules should be started and loaded on boot up as well.
Current CDS status: