You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer i would like the IOC startup bat scripts that are created in iocstartup/ioc_bats by running make iocstartups to allow additional options as well as just starting IOC. I would also like procserv to be started on demand from procServControl so there are not so many running on the system and consuming resources
Acceptance critera
using ILM200_01.bat as an example, running:
ILM200_01.bat or ILM200_01.bat start starts procserv
ILM200_01.bat stop stops procserv
ILM200_01.bat restart restarts procserv
ILM200_01.bat logrot closes and reopens log file. If you do this the following day it should create a new file with today's date which will not normally happen if no data is logged
ILM200_01.bat pid prints PID of process
After a start_ibex_server
check less procServ processes are running i.e. only those relevant to the configuration loaded, but all is working as before
check change config works. Note that non-needed iocs are stopped as before, but any procServ started earlier will remain.
check start/stop ioc from GUI to start/stop both a configuration present and non-configuration ioc work
check PSCTRL and BLOCKSERVER log files have no errors about failing to strat iocs
notes
when on branch at top of EPICS run make iocstartups to remake bats (this is also done by start_ibex_server)
If IOC is not generating any messages, then running logrot the following day creates a new file with today's date
running logrot may resolve the ProcServ: reproduce issue with "bad"/"locked" permissions #8555 issue on a case by case basis, it looks like permissions are OK after procserv stops so it may be the close/reopen from logrot is enough to clear things even if there is no day change
a startup argument is also added, on boot bats called with startup arg that only launches procserv for boot start items, and disable asyn autoconnect on non-boot items The related procservcontrol ticket will launch procserv on demand and also adjust asyn autoconnect
The text was updated successfully, but these errors were encountered:
FreddieAkeroyd
changed the title
ioc startup: make more flexible
ioc startup: make individual iocs bats more flexible and start procServ on demand from procServControl
Nov 1, 2024
As a developer i would like the IOC startup bat scripts that are created in
iocstartup/ioc_bats
by runningmake iocstartups
to allow additional options as well as just starting IOC. I would also like procserv to be started on demand from procServControl so there are not so many running on the system and consuming resourcesAcceptance critera
using
ILM200_01.bat
as an example, running:ILM200_01.bat
orILM200_01.bat start
starts procservILM200_01.bat stop
stops procservILM200_01.bat restart
restarts procservILM200_01.bat logrot
closes and reopens log file. If you do this the following day it should create a new file with today's date which will not normally happen if no data is loggedILM200_01.bat pid
prints PID of processAfter a
start_ibex_server
notes
make iocstartups
to remake bats (this is also done by start_ibex_server)logrot
the following day creates a new file with today's datelogrot
may resolve the ProcServ: reproduce issue with "bad"/"locked" permissions #8555 issue on a case by case basis, it looks like permissions are OK after procserv stops so it may be the close/reopen fromlogrot
is enough to clear things even if there is no day changestartup
argument is also added, on boot bats called with startup arg that only launches procserv for boot start items, and disable asyn autoconnect on non-boot items The related procservcontrol ticket will launch procserv on demand and also adjust asyn autoconnectThe text was updated successfully, but these errors were encountered: