This is an old revision of the document!
Occasionally, especially for Yg, eRc can refuse to connect or frequently drop out. The VNC session can also suffer some problems, is quite heavy on the network, and doesn't allow copy-paste. As an alternative, there is a text based backup control setup installed on the field system PCs.
You can access it either by:
Yg backup control
, et.c.This will present you with a a terminal window similar with a similar layout to e-RemoteCtrl.
To get the alarm system working, you need to stream the log files to ops2, or the PC with the log monitor. This can be done with ssh and tail, but there is a shell script on ops2 which does this for you. To transfer the current log file from pcfsyg to ops2 run:
~/steam_log yg
You can then point the log monitor to the file indicated by the script. Note: you will need to rerun this when the log file changes
By default, the cursor should be in the oprin
pane at the bottom of the window. If it isn't, you can change active panes by pressing “Ctrl+b” then an arrow key. The oprin
window is the same program that runs in the VNC, so tab-completion and up-arrows should work as expected.
As the script is very simple, there are a few quirks. Importantly, the log in the central pane will not update when the fs log is changes. You can either kill the session and restart it (see below), or highlight the central pane using Ctrl+b and the arrow keys, Ctrl+c to kill the tail, the running the tail program again by pressing up and enter.
The control setup runs in a tmux session, so it is persistent across window closes and disconnects. This means simply closing and reopening it will not reset the setup. Instead to reset the session:
:kill-session
You may also find the session in funny states if someone opens it in a small window, or if fs has been terminated.
The script runs a tmux session with the oprin
, monit2
, monit3
and monit5
programs built into the fs. The central pane runs tail -f
on the current log file, which is found by the lognm
program.
For the log in the central pane, it should be possible to follow the new log when the fs changes log files by looking for “log=”. Alternatively, the fs program itself could be run in the central pane, which would allow non-logging commands like “list” to be displayed there too.