Hi,
To declare an env var is allways for me a headache. I’d like to see a
flowchart to know from power on, what is executed, what is declared,
what inherited, what is known in consol shells, what is known in
photon/pterm, what is executed at each login, each shell session, etc…
There is maybe 20 different possibilities to declare something
somewhere. Not very clear, and we have to deal with posix env var and
qnx env var. Why HOSTNAME and _CS_HOSTNAME for example.
When will this part be clarified in the sysadmin guide??
Alain.
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
: Hi,
: To declare an env var is allways for me a headache. I’d like to see a
: flowchart to know from power on, what is executed, what is declared,
: what inherited, what is known in consol shells, what is known in
: photon/pterm, what is executed at each login, each shell session, etc…
: There is maybe 20 different possibilities to declare something
: somewhere. Not very clear, and we have to deal with posix env var and
: qnx env var. Why HOSTNAME and _CS_HOSTNAME for example.
: When will this part be clarified in the sysadmin guide??
We’re working on a Neutrino User’s Guide that will include this.
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
While I don’t share Alain’s dislike for enviornment variables, I do agree
that there should be documentation as to what happens/(should happen) where
and what’s it’s life span is (how long it is inherited by other processes
and which).
QSSL’s pat answer is “Go Get a POSIX Book”. But many systems (including
QNX6) still vary from a standard in this regard.
I would also like to see a list of files in one place that affect the system
“if they exist”.
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:3F044D21.2080901@icbt.com…
Hi,
To declare an env var is allways for me a headache. I’d like to see a
flowchart to know from power on, what is executed, what is declared,
what inherited, what is known in consol shells, what is known in
photon/pterm, what is executed at each login, each shell session, etc…
There is maybe 20 different possibilities to declare something
somewhere. Not very clear, and we have to deal with posix env var and
qnx env var. Why HOSTNAME and _CS_HOSTNAME for example.
When will this part be clarified in the sysadmin guide??
Alain.
Bill Caroselli <qtps@earthlink.net> wrote:
: While I don’t share Alain’s dislike for enviornment variables, I do agree
: that there should be documentation as to what happens/(should happen) where
: and what’s it’s life span is (how long it is inherited by other processes
: and which).
: QSSL’s pat answer is “Go Get a POSIX Book”. But many systems (including
: QNX6) still vary from a standard in this regard.
Funny, I thought the pat answer that I used this time was that we plan to
document it.
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
Well I meant in general!
“Steve Reid” <stever@qnx.com> wrote in message
news:be257s$rj3$1@nntp.qnx.com…
Bill Caroselli <> qtps@earthlink.net> > wrote:
: While I don’t share Alain’s dislike for enviornment variables, I do
agree
: that there should be documentation as to what happens/(should happen)
where
: and what’s it’s life span is (how long it is inherited by other
processes
: and which).
: QSSL’s pat answer is “Go Get a POSIX Book”. But many systems (including
: QNX6) still vary from a standard in this regard.
Funny, I thought the pat answer that I used this time was that we plan to
document it.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems