VxWorks: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
systemctl start rsh.socket | systemctl start rsh.socket | ||
systemctl status rsh.socket | systemctl status rsh.socket | ||
Make sure all vxWorks controllers are in .rhosts file. That file is in the home directory if the user we are booting from, for EPICS controller it is user 'epics'. | |||
== boot from RHEL5 == | == boot from RHEL5 == | ||
Revision as of 12:08, 13 January 2026
boot from RHEL9
Do follwoing on vxWorks boot host, currently clon01):
yum install rsh-server systemctl enable rsh.socket systemctl start rsh.socket systemctl status rsh.socket
Make sure all vxWorks controllers are in .rhosts file. That file is in the home directory if the user we are booting from, for EPICS controller it is user 'epics'.
boot from RHEL5
yum install rsh-server enable rsh (part of xinet) restart xinet .rhosts file
useful info
tsconnect <iocname>
reboot: ctrl-X exit: ~.
classc1:
classc3:
boot device : ei processor number : 0 host name : clon00 file name : /home/epics/kernel/5.2/coda/vx162nowd_p-16MB inet on ethernet (e) : 129.57.160.19:fffffc00 host inet (h) : 129.57.167.5 gateway inet (g) : 129.57.160.1 user (u) : epics flags (f) : 0x8 target name (tn) : classc3 startup script (s) : $IOC_root_classc3/ioc/classc3/startup