Mac OS: shell not recognising scp [closed] - bash

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I'm trying to execute the below command on my new MacBook and was getting the '-bash: sudo scp: command not found' error.
Please help me fixing this issue.
sudo scp -i Pem_File_Name.pem PHP_File_Name.php centos#Host_Path:/var/www/html/Folder_Name/
The Pen_File_Name, PHP_File_Name and Host_Path are replaced with their respected values.
Thanks in advance.
Geeth.

From the error, I'd guess that you have something other than a normal space (maybe a non-breaking space) between "sudo" and "scp". The reason I think this is that the error message says the command "sudo scp" was not found -- but the command should be "sudo" (which should then run "scp" as a separate command). This means that for some reason bash is treating "sudo scp" as a single word instead of two.

Related

% sign in terminal command line rather than $ sign [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I am using Terminal on MacOS. My main concern is that I’m commonly seeing command lines starting with the ‘$’ sign.
My command lines begins with a ‘%’ sign. Does this matter? If so, what is the reason?
The reason is that bash is no longer the default shell in macos. The default shell is now zsh which has certain advantages, such as floating-point operators.
You may set the Terminal default shell back to bash if needed. It's path is simply /bin/bash

Can I run a bash command that came to my mind while writing another? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
When I'm in the terminal, I find myself writing a bash command and then I remember that I had to use another command first.
Example:
user$ python manage.py runserv...
and I remembered that I had to use
pip install -r requirements.txt
first for any new package.
Is it possible to run it without having to erase my first still incomplete command?
Thanks
Use ctrl+a to go to the beginning of the line, then ctrl+k to yank your current line to the cut buffer.
Run your new command, then press ctrl+y to "yank" the text back out, inserting it at the current cursor position.

Use over ssh automatically a different shell than the users default [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
We use as the default shell: Bash on our servers but some of us like zsh more, so we searching for a way, to set ZSH automatically.
chsh to zsh i not an option.
How about
ssh -t remote_user#remote_host zsh
?
Depends on how 'automatically' do you want it.
If you want that just ssh -t remote_user#remote_host should give you zsh prompt, then you should think on the lines of bash functions probably. but IMO, that would be a really bad way to do it.

in Terminal, what is the difference between normal mode and switching to bash? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
When you are in Terminal, you are greeted with a prompt saying:
computer_name:~ directory user$ (command input)
Then if you use the command "bash", the prompt changes to:
bash-3.2$ (command input)
Now I understand that when you use a command like "python", you are taken into the Python interpreter, but it seems like pretty much all the same commands as usual work when you switch to Bash. Could someone explain what (if anything) is happening here?
When you type bash you are taken into a new Bash instance. If you press Ctrl + D you will exit. OSX uses Bash as default shell.

Accidentally killed /bin/bash process.. what should i do? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
as the topic suggest, i accidentally killed the wrong process. nothing is working for me now. what should i do?
I have tried to install, reinstall but it does not work.
whatever cmd i type just returns nothing
ls
cmd
pwd
Assuming that you had ssh'ed to the machine and killed your own shell, I would suggest that you just try to ssh to the machine again and start over.
If that doesn't work, reboot the server via the AWS console.

Resources