|
- What is the difference between . . and source? [duplicate]
When the script is done, any changes that it made to the environment are discarded script The above sources the script It is as if the commands had been typed in directly Any environment changes are kept source script This also sources the script The source command is not required by POSIX and therefore is less portable than the shorter
- Source vs . why different behaviour? - Unix Linux Stack Exchange
source is a shell keyword that is supposed to be used like this: source file where file contains valid shell commands These shell commands will be executed in the current shell as if typed from the command line
- Cant use `source` from cron? - Unix Linux Stack Exchange
When I try to use source from the cron job (I have tried both directly in crontab and in a script called by crontab) it doesn't seem to work I made a simplified version of my project to demonstrate the issue (including rsyslog for logging): Dockerfile: FROM debian:jessie # Install aws and cron RUN apt-get -yqq update
- What is the difference between eval and source dev stdin?
Your example provides the same result, but the purpose of eval and source is different source is usually used for providing a library for other scripts, while eval is used only to evaluate commands eval should be avoided if possible, because there is no guarantee that the eval 'ed string is clean; sanity checks must be done, using subshell
- bash - Revert . or source - Unix Linux Stack Exchange
I accidentally sourced the wrong environment from a script Is there any way to 'unsource' it or in other words to revert it and restore the previous environment? The obvious answer is to start fr
- What is the difference between . and source in shells?
2 source is there for readability and self-documentation, exists because it is quick to type The commands are identical Perl has long and short versions of many of its control variables for the same reason
- sudo: source: command not found - Unix Linux Stack Exchange
34 source is a shell builtin, so it cannot be executed without the shell However, by default, sudo do not run shell From sudo Process model When sudo runs a command, it calls fork (2), sets up the execution environment as described above, and calls the execve system call in the child process If you want to explicitly execute shell, use -s option:
- Opposite of the `source` command - Unix Linux Stack Exchange
It is not source that is setting the variables in your environment, but the export statements in the file which you source So the opposite of source could be source, if you source a different file which unset s all the same variables
|
|
|