New answers tagged

0

Make sure your masterScript.sh is executable by doing chmod +x masterScript.sh If the script is not executable the bash command cannot run it and you'll get these kind of error messages.


0

I tried this out .. I simply made it alias masterScript="cd /home/arun/Desktop/scripts && myMasterScript.sh


0

Just create a function: function masterScript() { if [ -e /home/arun/Desktop/scripts/myMasterScript.sh ] then bash /home/arun/Desktop/scripts/myMasterScript.sh fi } And make sure your script is executable: chmod 755 /home/arun/Desktop/scripts/myMasterScript.sh


2

They are synonymous. From the shell.c file of bash-4.3 source: long_args[] = { .... { "init-file", Charp, (int *)0x0, &bashrc_file }, .... { "rcfile", Charp, (int *)0x0, &bashrc_file }, .... }; As you can see they are defined the same way and also works the same way. The parameter bashrc_file stores the filename. For further assurance, the ...


0

Could be the same problem: Try resetting your path with this command: export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin (Source)


1

When you call source ~/.bashrc you reload your ~/.bashrc configuration only for that current terminal session. You have to do it for all other existing terminal sessions as well if you want to reload your ~/.bashrc


-1

The cause might be a read-only folder. In my case the 'Make' file that calls nvcc was in a read-only folder. Changing the folder permission settings solved my problem.


0

It is common to when using bash to place the profile initialization in .bash_profile, which is read only by bash on login, whereas other shells have historically shared .profile. This allows you to place bash-specific commands in .bash_profile. Use of the following is commonly done to pull in the aliases that are defined in .bashrc: # Get the aliases and ...



Top 50 recent answers are included