Date: Wed, 27 Feb 2002 23:33:16 +0100 From: Rickard Borgmäster <doktorn@realworld.nu> To: Mike Makonnen <mike_makonnen@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: System-wide environment variables Message-ID: <20020227233316.42430b8e.doktorn@realworld.nu> In-Reply-To: <1014735740.677.25.camel@blackbox.pacbell.net> References: <20020226030324.4a94cc33.doktorn@realworld.nu> <1014689577.677.0.camel@blackbox.pacbell.net> <20020226025447.GA21944@dan.emsphone.com> <1014696241.677.5.camel@blackbox.pacbell.net> <20020226051544.GC1931@raggedclown.net> <1014735740.677.25.camel@blackbox.pacbell.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Feb 2002 07:02:20 -0800
Mike Makonnen <mike_makonnen@yahoo.com> hit the keyboard and punched:
> > Any such program will inherit the exported environment
> > from it's parent process. Examination of /etc/rc will lead
> > you to see what they will be for startup daemons and such like.
> > Examination of the non-interactive behaviour of a shell startup
> > script (if one is used) will tell you what that environment will
> > be. Use of the "env" command may also help.
>
> I can't remember what he originally wanted this for, but the solution
> might be to put whatever he needs this for in a wrapper script.
I just want to set a few variables for all uses, no matter wether
they login from shell or by gdm. Such as:
export PS1=$'[ \\u@\\h:\\w ] \\$ '
Why do I need a wrapper?
--
Rickard
.--. .--.
.----------------------------------------. | | | | .-.
| Rickard Borgmäster | | | | |/ /
| doktorn@sub.nu | .-^ | .--. | <
| http://doktorn.sub.nu/ | ( o | ( () ) | |\ \
`----------------------------------------' `-----' `--' `--' `--'
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020227233316.42430b8e.doktorn>