I just put the stuff I want in /.cshrc.
Regards,
Alex Johnson
10707 Haddington
Houston, TX 77063
713.722.2859(v)
713.722.2700(sb)
713.932.0222(f)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Joe Markham [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, October 19, 2000 10:33 AM
To: Foxboro DCS Mail List
Cc: Winston Jenks (E-mail)
Subject: RE: Searching for lost environment variables
I grabbed the environment from the VT100 window you get from the
tools menu
(any child of the display manager/foxview process gets the extra
environment
variables), saved it as a file and just run it after I log in from
some
other machine (just start a new shell - for example: ksh
/opt/mydir/myprofile). It is a bit cumbersome, but it works for me.
I also
added a shortcut to the olwm menu to run a cmdtool with this already
done
for me. I'll look it up for you when I get back on site, if you
like.
-JAM
-----Original Message-----
From: Winston Jenks [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 19, 2000 9:44 AM
To: Foxboro DCS Mail List
Subject: Searching for lost environment variables
List,
Apparently losing things is all the rage now. I have lost my
environment
variables. When I start the cmdtool from the olwm desktop I get all
kinds
of good variables like MANPATH, etc. But when I log in as root from
another machine I just get what is defined in the likes of
/etc/profile,
~/.profile, ~/.cshrc and ~/.login (depending on my shell).
So I am led to believe that these environment variables that appear
in the
cmdtool are inherited from the process that started it. Where does
that
guy get his variables?
Winston Jenks
Technical Director, Cape Software, Inc.
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company.
All
postings from this list are the work of list subscribers and no
warranty
is made or implied as to the accuracy of any information
disseminated
through this medium. By subscribing to this list you agree to hold
the
list sponsor(s) blameless for any and all mishaps which might occur
due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company.
All
postings from this list are the work of list subscribers and no
warranty
is made or implied as to the accuracy of any information
disseminated
through this medium. By subscribing to this list you agree to hold
the
list sponsor(s) blameless for any and all mishaps which might occur
due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
