xxx.sh fails to detect a running IOC if the IOC is named "cc" - Githubissues

epics-modules / xxx

APS BCDA synApps module: xxx

http://epics-modules.github.io/xxx

Other

5 stars 6 forks source link

xxx.sh fails to detect a running IOC if the IOC is named "cc" #36

Closed kmpeters closed 4 years ago

kmpeters commented 4 years ago

If the IOC is named xxx, xxx.sh start successfully starts the IOC, /proc/<pid>/cwd points to the iocxxx directory, and xxx.sh status correctly reports that the IOC is running.

If the IOC is named cc, cc.sh start successfully starts the IOC, /proc/<pid>/cwd points to the IOC's top directory, and cc.sh status fails to report that the IOC is running. It is possible to manually connect to the screen session.

This could be a bug in RHEL 7.7.

kmpeters commented 4 years ago

This isn't an issue for IOCs based on xxx. It must be specific to an IOC named cc that came from another source.

tl;dr not an issue; nothing to fix.