| | 10 | |
| | 11 | '''Here I make a numbered list. ''' |
| | 12 | # We receive an email notifying us that hpf has lost |
| | 13 | tcs metadata. We may also hear an alert from netsounds.sh |
| | 14 | (although I have never heard anything). |
| | 15 | |
| | 16 | # Try to perform a graceful tims shutown by going to the |
| | 17 | rasession scripts window and issuing: "tims het shutdown" |
| | 18 | |
| | 19 | # if list item 2 is not successful, go to the tims client window (in |
| | 20 | rasession this is the upper-right window). In this window |
| | 21 | we enter a cntrl-C to kill the timhet run that is presumed |
| | 22 | to be hung. |
| | 23 | |
| | 24 | # We hit the "TCS client restart" button in the RA Ops web |
| | 25 | to restart the timshet communication. We observe output |
| | 26 | in the tims client window (rasession) that verities that the |
| | 27 | restart has occurred. --OR-- You can issue "timshed" in the |
| | 28 | rasession client window. |
| | 29 | |
