Why is my shell changing when I use 'sudo'? [closed] - macos

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.

Related

Sudo Error: "Sorry, try again." when I tried to install Elixir [closed]

Closed. This question is not about programming or software development. 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 days ago.
Improve this question
I am trying to install Elixir on the computer I'm using so I ran sudo port install elixir. Upon running this command Sudo asks for the password. There is no password set so I simply pressed the return key, but when I did this it gave me the error Sorry, try again. To add, there is only one account on the computer. I am using a Mac running MacOS Catalina.

mac osx clean command not working under tmux [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 months ago.
Improve this question
As the title says the error is "terminals database is inaccessible":
ยป clear
terminals database is inaccessible
macOS Monterey 12.4
Issue only occurs under tmux + zsh and googling hasn't helped.
You can try to configure the default terminal to xterm by adding
set -g default-terminal xterm-256color
to your ~/.tmux.conf

Adding a command line call on Macbook startup [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 6 years ago.
Improve this question
I'm running the latest Sierra version, and every time I reboot I need to execute
mysql.server start
I'd like to simply add this command to a startup script, but I've spent an hour looking at setting up daemons, etc, but I feel like it shouldn't be that difficult.
Is there an easy way to put this in some sort of startup script so every time I start my macbook it's run in the background?
Any help would be appreciated!
run this in terminal
ln -sfv /usr/local/opt/mysql/*.plist ~/Library/LaunchAgents
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
providing that mysql installed with brew

SSH not working after OSX 10.10.4 upgrade (vagrant) [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 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.

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