Start as_server via "sudo systemctl start waae_server.ACC.service" works fine. But if the process crashes : the command "sudo systemctl status waae_server.ACC.service" still returns as if systemctl running although process "as_server -A ACC" is gone.
So "/sys/fs/cgroup/systemd/system.slice/waae_server.ACC.service" does not provide the pid info to systemdService
I expect when the component is started with systemctl command, the systemdService is aware when the process is killed.
when started as_server with init scripts( waae_server.ACC or CA-WAAE) and killed via "kill -IO pid", the next start it seems the start is OK but is not OK .
This is probably caused by the existing of the previous lock-file "/var/lock/subsys/waae_server.ACC"
I excpect, when the process is crashed or killed, the lock file is removed when the next start is launched and the previous process is gone, so the component really starts.
Conclusion : both ways of starting the Sever/scheduler component has disadvantages.
Release : 11.3.6
Component : CA Workload Automation AE (AutoSys)
Linux: rhel 7 Onwards
- Autosys scripts are defined to start with init.d but if its adopted by systemd it stats but with some warnings.
- Autosys is recommended to start using init.d