Help with the currently set environment variables!!
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i think /etc/profile is what your looking for (note this is the universal localation for it, each usr should ahve there own profile file were tehy decalre variables, look in the /etc/passwd file to see were teh location for the file should be (if its not there then /etc/profile is the file to use) optionaly you can declare variables in the startupscripts i think
Is the difference between 'printenv' and 'set' that printenv lists all (and only) general variables and the set builtin lists those plus bash-specific variables?
set > set.out
produces a much larger file with more variables. The printenv man page has been info-ized (says much of nothing except directing me to damn info pages) so I don't know, but that's my guess based on the differences of the two files.
Just took a quick look at the man pages. Looks like 'printenv' will display
only exported variables, while 'set' will display in addition those that
haven't been exported. (set is also a BASH builtin, while printenv isn't).
I'm open to criticism on the above.
*edit*
No, I tried it. There's more to it than that. Some BASH-specific global
variables are missing from printenv's output, as you pointed out.
Hm. I just loaded csh (which has a 'printenv' builtin) and doing 'printenv > file' produces yet another output - almost identical to the external printenv as run by bash, but with a handful of others. But running the external printenv *with* csh produces an identical file to the csh builtin.
Dunno where to go with any of this, but I was just curious. I've always used the 'set' builtin and had never tried 'printenv'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.