Bug 989443 - Would be nice to have an ENV var pointing to app's pid file
Summary: Would be nice to have an ENV var pointing to app's pid file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-29 09:30 UTC by Oleg Fayans
Modified: 2016-12-01 00:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-24 04:02:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Oleg Fayans 2013-07-29 09:30:33 UTC 
Description of problem:

nodejs-0.6 has the following ENV variable:
OPENSHIFT_NODEJS_PID_DIR

It would be nice if all the cartridges had something like OPENSHIFT_APP_PROCESS_PID pointing to the pid file of the app. 

Version-Release number of selected component (if applicable):

devenv-stage_424

How reproducible:

Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Michal Fojtik 2013-08-20 13:43:44 UTC 
What if there are more than one processes running in one cartridge? Typically more than one Apache service?
Comment 2 Michal Fojtik 2013-11-13 13:23:24 UTC 
Also for the Zend server for example, there are many services running in parallel so it is not clear to me what PID will should OPENSHIFT_ZEND_PID for example advertise.
Comment 3 Oleg Fayans 2013-12-12 09:28:39 UTC 
Not actual any more. I have found a way to find app's pid without the ENV variable. It was needed for testcases that check the hot_deploy functionality
Note You need to log in before you can comment on or make changes to this bug.