Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IMPROVE] Multiinstance identification of pep instances ps #306

Open
cesarjorgemartinez opened this issue Apr 27, 2016 · 2 comments
Open
Labels

Comments

@cesarjorgemartinez
Copy link
Contributor

ps -efa|grep pep
pepproxy 8313 1 0 10:08 ? 00:00:00 node /opt/pepProxy/bin/pepProxy
pepproxy 8361 1 0 10:08 ? 00:00:00 node /opt/pepProxy/bin/pepProxy

We can use something else STH:
ps -efa|grep sth
sth 15134 1 3 10:14 ? 00:00:00 /usr/bin/node /opt/sth/bin/sth /opt/sth/conf/sth_sth.conf

@dmoranj
Copy link
Contributor

dmoranj commented Apr 29, 2016

Please add some more text to the description, I can barely understand what you are talking about. Do you want me to change how PEP instances look in a linux ps command? Is that even possible?

@cesarjorgemartinez
Copy link
Contributor Author

Yes, we can identify different instances if in the start add the name of the instance, or path to instance configuration.
In STH we have:
https://github.com/telefonicaid/fiware-sth-comet/blob/master/rpm/SOURCES/etc/init.d/sth
su ${COMPONENT_USER} -p -c "${NODE_EXEC} ${COMPONENT_DIR}/bin/sth ${instance} 2>&1 | tee -a ${LOG_DIR}/${NAME}.log & echo $! > ${STH_PID_FILE}"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants