copy and paste this google map to your website or blog!
Press copy button and paste into your blog or website.
(Please switch to 'HTML' mode when posting into your blog. Examples: WordPress Example, Blogger Example)
Input Form:Deal with this potential dealer,buyer,seller,supplier,manufacturer,exporter,importer
(Any information to deal,buy, sell, quote for products or service)
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
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
What is the difference between ~ . profile and ~ . bash_profile? The original sh sourced profile on startup bash will try to source bash_profile first, but if that doesn't exist, it will source profile Note that if bash is started as sh (e g bin sh is a link to bin bash) or is started with the --posix flag, it tries to emulate sh, and only reads profile Footnotes: Actually, the first one of bash_profile, bash_login, profile See also: Bash
How to export variables from a file? - Unix Linux Stack Exchange A dangerous one-liner that doesn't require source: export $(xargs <file) It can't handle comments, frequently used in environment files It can't handle values with whitespace, like in the question example It may unintentionally expand glob patterns into files if they match by any chance It's a bit dangerous because it passes the lines through bash expansion, but it has been useful to me when I
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
Use config file for my shell script - Unix Linux Stack Exchange 36 source is not secure as it will execute arbitrary code This may not be a concern for you, but if file permissions are incorrect, it may be possible for an attacker with filesystem access to execute code as a privileged user by injecting code into a config file loaded by an otherwise-secured script such as an init script
source - Passing variables to a bash script when sourcing it - Unix . . . Michael Mrozek covers most of the issues and his fixes will work since you are using Bash You may be interested in the fact that the ability to source a script with arguments is a bashism In sh or dash your main sh will not echo anything because the arguments to the sourced script are ignored and $1 will refer to the argument to main sh When you source the script in sh, it is as if you just