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 7 years ago.
Improve this question
I upgraded to 10.10.4 this morning and after I had upgraded, when I attempted to SSH into a local Vagrant dev box, it resulted in access denied too many authentication attempts.
Run ssh-add -D to delete all your keys from the SSH agent.
Then add them again using ssh-add -k path_to_to_key
I had the same issue with Vagrant and this fixed the problem.
Related
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 1 year ago.
Improve this question
I'm running version 20H2 (OS Build 19042) on windows home edition, i built a linux kernel and im trying to set it up on my machine by configuring the .wslconfig file as follow:
[wsl2]
kernel=c:\\wslkernel\\bzImage
everything is at place according to the documentation - https://learn.microsoft.com/en-us/windows/wsl/wsl-config
any ideas what could have gone wrong?
turns out i was running wsl version 1 and not wsl2 - for the full thread on the issue:
https://github.com/microsoft/WSL/issues/6728
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 4 years ago.
Improve this question
I'm able to login passwordless with putty after adding the key to my server and configuring putty (gui) with session. I'm unable to login passwordless with plink. How do I do this?
Use -i option to use the particular private key or just use -load option with the session that you created in putty gui.
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
I have an EC2 instance I"m trying to copy all the data inside of it into my drive.
the command
"scp -r / /users/seraph/targetdirectory"
does not work and returns
"no such file or directory"
On the OS X machine:
scp -r remotehost:/ /some/local/path
Better yet, use rsync so that you can support resume and deltas:
rsync -e ssh -avz remotehost:/ /some/local/path
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
When I run sudo su on my mac os x (10.8.5) MacBook Air, the shell changes for some reason:
bos-mp2o6:~ rabdelaz$ sudo su
Password:
sh-3.2#
What's up with that?
The only thing I've done is install Heroku Toolbelt and, after getting sudo: unable to cache user root, already exists, rebooting.
When you use sudo su, it runs the superuser's .bashrc, so you get its prompt instead of your own.
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.