How does /usr/bin/env know which program to use?
When I use the shebang #!/usr/bin/env python to run a script, how does the system know which python to use? if I look for a python bin path in the environment variables I find nothing.
environment-variables
mktemp on macOS not honouring $TMPDIR
I’ve noticed this before, but it was brought up again as I was answering “How to move directory into a directory with the same name?“:
Isn’t $HOME supposed to be the location of the user’s home directory?
I’m having trouble with a web application I’m writing: The web application, which runs as user nobody, needs to launch an inkscape process to manipulate some SVG files. Because this runs as user nobody, there is no home directory. What I am doing is creating a temporary directory under /tmp and trying to set that as the home directory via export HOME=/tmp/someUniqueId. I then set a few things in that “temporary” home directory, like a symlink .fonts to the folder for the font files to use.
Understanding environmental variables in different contexts
Trying to understand the behaviour of the environment in Linux (Ubuntu 13.04 concretely), I’ve find different situations where setting envirionment variables are used or defined for/in different contexts. For example, if I check, locale, I get:
What’s the difference between “export” and “setenv”?
What’s the difference between export and setenv?
How to export variable for use with sudo?
On Slackware, using sbopkg permits one to build a package from source. Repos is not big as Debian, but it’s nice.
What is the difference if I start bash with “/bin/bash” or “/usr/bin/env bash”?
In shell scripts one specifies language interpreter on shebang(#!) line. As far as I know, it is recommended to use #!/usr/bin/env bash because env is always located in /usr/bin directory while location of bash may vary from system to system. However, are there any technical differences if bash is started directly with /bin/bash or through … Read more
Why is passing the secrets via environmental variables considered “extremely insecure”?
Passing secrets (password) to a program via environmental variable is considered “extremely insecure” according to MySQL docs and as poor choice (from security aspect) across other resources.
pass 1 environment variable using sudo
Is this a correct way for passing an environment variable in sudo ?