Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've just created a new user in my machine with adduser --system --group studio for audio purposes, and everything went ok until I've tried to open a terminal, which opened and closed immediately.
I've tried using other terminals (xfce4-terminal, Xterm and UXterm) and the problem persisted.
Then I've tried logging in a tty, which showed a strange behavior: it logs in, shows that message Last login: bla bla bla, and quickly comes back to login screen. So I think the problem is with bash and this specific user. Logging on a tty with the older user still works.
I've also tried creating the files .bashrc and .profile (actually copying them from the working user), but it didn't fixed the problem either.
This is a very strange behavior for me, and I've never seen this before. As I can't access any shell from this user, I'm not able to diagnose the problem. I've checked dmesg and all logs possible and nothing shows up when the error happens. I'm using Debian Wheezy and XFCE4. My uname -a is:
Linux t4rkus-nb 3.2.0-4-rt-686-pae #1 SMP PREEMPT RT Debian 3.2.35-2 i686 GNU/Linux
Why are you passing the --system flag? From the manpage:
The new system user will have the shell /bin/false (unless overridden
with the --shell option), and have logins disabled. Skeletal
configuration files are not copied.
Meaning the new user has /bin/false as the shell, which immediately exists when you try to log in with it.
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 9 years ago.
Improve this question
I added something to my bash_profile while trying to add Playframework to my path and something got messed up badly.
I added the following line to my .bash_profile
export PATH=$PATH:the path to my play excitable
then I saved everything and restarted my terminal. I can no longer do anything from my terminal. I can't cd into any directory, I can no longer find java, I can't open vi or nano.
I found this thread on SuperUser that suggested opening a different terminal and changing the bash profile.
I tried opening bash by typing
/bin/bash
and I was successfully able to open another terminal but I still don't have access to any of the regular unix commands. I still wasn't able to open vi or nano to remove the line that is causing the problem.
I tried downloading a new terminal application without any luck.
I tried turning on hidden files so that I can just change the file with a text editor by running the following command:
defaults write com.apple.finder AppleShowAllFiles TRUE
but since my terminal isn't working that didn't work either.
How can I fix my computer.
While this is offtopic for stackoverflow, it's also pretty simple to fix:
Start Terminal.app.
Reset $PATH:
$ export PATH=/bin:/usr/bin:/usr/local/bin
Fix ~/.bash_profile:
$ vi ~/.bash_profile
Or you can avoid setting $PATH at all with:
$ /usr/bin/vi ~/.bash_profile
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
My PhpStorm terminal doesn't work properly on Linux Mint
In Settings > Tools > Terminal my Shell path is "/bin/bash"
When I open Terminal window in PhpStorm and call ls command work properly but php and sudo and etc not work and return bash: php: command not found
Original terminal app:
Terminal in PhpStorm:
PhpStorm CLI interpreters:
Does the issue persist if your start PhpStorm from terminal, either with the command line launcher or with bin/phpstorm.sh?
When being launched from desktop/System menu, PhpStorm only sees environment variables configured in login shell, but not in interactive shell configuration files (like .bashrc or .zshrc).
Possible workarounds:
Workaround 1: make required variables available in a login shell by moving them to the corresponding shell profile config
Workaround 2: run IDE from a terminal
Workaround 3: edit the desktop launcher and set command to /path/to/shell -l -i -c "/path/to/phpstorm.sh" (make sure that the shell you specified there has the needed variables configured in its interactive shell configuration file)
see also https://youtrack.jetbrains.com/issue/IDEABKL-7589
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 just switched to zsh as my default Mac OS terminal shell. However, I found it won't automatically hit the ~/.profile file. After researching on Google, it looks like it can be solved by adding the following command in ~/.zprofile to emulate whatever in ~/.profile:
emulate sh -c '~/.profile'
However, I got the follwoing error when terminal starting up:
zsh:1: permission denied: /Users/XXX/.profile
Any idea why this is happening?
To accomplish your goal, you'd have to use:
emulate sh -c 'source ~/.profile' # Note the `source`; alternatively, use `.`
Without the source, ~/.profile would run in a subshell, which defeats your intent (exports wouldn't "stick"); you have to source that other file.
(The specific error you saw stems from an attempt to execute ~/.profile directly, without its being marked as executable. Note that shell profiles normally needn't be executable, because their only purpose is to be (automatically) read by a shell. It's a moot point, however, given that sourcing from within a shell is needed.)
As for what zsh initialization file to put the command in:
On macOS, if you've made zsh your default shell, then ~/.zprofile works, as all shells you'll open in a terminal will be login (zsh) shells, which will read that file.
Generally, though, ~/.zshrc is the better choice, as that file gets sourced by any interactive zsh shell, whether it's a login shell or not. It's also the file to use with the Oh My Zsh framework.
Sounds like you should be using .zshrc
Add this to ~/.zshrc:
EXPORT JAVA_HOME="whatever"
And type $ source ~/.zshrc in your terminal window, or start a new shell instance.
Follow up:
this article lists the startup files loading order which clarifies the confusion.
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
I added something to my bash_profile while trying to add Playframework to my path and something got messed up badly.
I added the following line to my .bash_profile
export PATH=$PATH:the path to my play excitable
then I saved everything and restarted my terminal. I can no longer do anything from my terminal. I can't cd into any directory, I can no longer find java, I can't open vi or nano.
I found this thread on SuperUser that suggested opening a different terminal and changing the bash profile.
I tried opening bash by typing
/bin/bash
and I was successfully able to open another terminal but I still don't have access to any of the regular unix commands. I still wasn't able to open vi or nano to remove the line that is causing the problem.
I tried downloading a new terminal application without any luck.
I tried turning on hidden files so that I can just change the file with a text editor by running the following command:
defaults write com.apple.finder AppleShowAllFiles TRUE
but since my terminal isn't working that didn't work either.
How can I fix my computer.
While this is offtopic for stackoverflow, it's also pretty simple to fix:
Start Terminal.app.
Reset $PATH:
$ export PATH=/bin:/usr/bin:/usr/local/bin
Fix ~/.bash_profile:
$ vi ~/.bash_profile
Or you can avoid setting $PATH at all with:
$ /usr/bin/vi ~/.bash_profile
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Setup: Mac OSX 10.6.8, Terminal 2.1.2 (273.1)
My Terminal sometimes becomes unresponsive after I enter certain commands. An example is when I put a tail on the catalina.out file though it happens at other times as well.
An example of the steps I take when im putting a tail on.
I go to the startup folder
cd /Applications/Tomcat/apache-tomcat-6.0.16/bin
Enter the start command
sh startup.sh
Go to my logs folder
cd /Applications/Tomcat/apache-tomcat-6.0.16/logs
And put a tail on the catalina.out file
tail -f catalina.out
This all works fine and the terminal window displays the processes as they are being used. However, if I try to type something else in Terminal it becomes unresponsive. If I press the Up or Down arrow to get list the previous commands all I get is for UP is "^[[A" and "^[[B" for DOWN.
When I type e.g. "cd .." and press enter nothing happens
Why does Terminal become unresponsive and how can I make it execute my commands? At the moment I have to quite Terminal each time this happened which is a bit annoying.
don't use tail -f
Instead when you want to run it instead of
sh startup.sh
run:
sh catalina.sh run
It will log everything to the window.
OR you can just open another terminal and do your tail -f from there!