Alternately, you can get a console to the target ioc-b34-bd32 using iocConsole and ssh as user "laci" from there:
iocConsole ioc-b34-bd32 When prompted to enter the "login" username as below, enter "laci". Welcome to Buildroot ioc-b34-bd32 login: No password is needed. Just hit Enter an you will get the shell prompt "$". Ensure the caRepeater process is running on this CPU. (b) Ensure your IOC is not already running as below:
$ screen -ls No Sockets found in /tmp/uscreens/S-laci. You can also look for your application under all running processes and make sure one is not already running: If it was running already, then you may get something as below:
$ ps -ef | grep MyTest 2085 laci 0:07 bin/MyTest iocStartup.cmd (c) Change to $IOC/ioc-b34-bd32 and from there start your ioc as a foreground process as below: $ pwd /home/laci $ ls -lt total 0 lrwxrwxrwx 1 root lcls 45 Nov 5 15:11 bld -> /afs/slac/g/lcls/epics/iocCommon/ioc-b34-bd32 $ cd bld Ensure that 'startupConsole-laci-rt.cmd' is in your current directory. $ ls -lt | grep startupConsole-laci-rt.cmd -rwxrwxr-x 1 8396 1020 1225 Nov 5 15:22 14. How do I start my ioc automatically every time my server boots up?You can start your ioc as a background process that will start up everytime your Linux server reboots, as follows: In $IOC/ioc-b34-bd32, you can add another script 'startup-laci-rt.cmd' that lets you start your EPICS-based ioc as a background process in your host. Invoke this script from $IOC/ioc-b34-bd32/startup.cmd: su laci -c /usr/local/lcls/epics/iocCommon/eioc-b34-bd32/startup-laci-rt.cmd The above line starts another shell so that the user called "laci" can start the IOC Process as opposed to the "root" account Remember, the kernel modules can only be loaded onto the kernel with "root" permissions but iocs can be run by users. 'startup-laci-rt.cmd' executes the EPICS-based IOC startup script and detaches it using the linux screen program It contains the following lines which are similar to what we have in startupConsole-laci-rt.cmd:
Start the ioc as a foreground process:
./startupConsole-laci-rt.cmd You can observe the viocb34bd32 go through the boot process. If you had an EVR230 and it was initialized correctly, you may see something as below before iocInit():
ErConfigure(0, 0, 0, 0, 1) Try EvrOpen, device = /dev/era3 EVR Found with Firmware Revision 0x11000007 Found a PMC_EVR /dev/era3 Verify if all your drivers, modules and databases loaded correctly. If you used iocConsole, you can scroll back and forth in the screen using <CTRL> A-[ and <CTRL>-A-]
If everything went well, you must get your interactive ioc shell prompt as below: vioc-b34-bd32> (d) Once the ioc is started, you can interact with vioc-b34-bd32 from any LCLSDEV host via ssh laci@ioc-b34-bd32: To attach a screen session:
screen -r vioc-b34-bd32 To detach from a screen session: <CTRL> A D
(e) To exit an EPICS IOC Process type exit at the IOC Shell and you will be back at the "$" prompt:
vioc-b34-bd32>exit If the IOC hangs too long while trying to exit, use <CTRL> C |