-1

I have written a shell script named startup.sh which does a lot of things (basically start a lot of things for me after turning on my local machine) - here is an excerpt:

#!/bin/bash
gnome-terminal --tab &
veracrypt --auto-mount favorites &
thunderbird &
~/Application/IDEA/bin/./idea.sh &
/usr/bin/slack &
echo myuser mypass | skypeforlinux --pipelogin &
sh bsync-project-folder.sh &
exit

Open a console window and do:

. startup.sh

The shell script is executed and the window is closed afterwards.

Also working:

sh startup.sh

OR

./startup.sh

The shell script is executed and the terminal window stays open - however it does not return to the console and have to stop script execution with CTRL + C (no matter if I execute with the command line interpreter or with ./).

However I want a clean exit of my script and then return to the same console with a success message. What am I missing?

Improve this question
6
  • Check out What is the difference between executing a Bash script vs sourcing it?. Commented Nov 14, 2018 at 13:28
  • Also, possible duplicate of What is the difference between sourcing ('.' or 'source') and executing a file in bash?. Commented Nov 14, 2018 at 13:30
  • Does the veracrypt command return you to the prompt if you run it interactively? Also, you say it's an excerpted script; you may not have posted the offending line-- look for one that does not end in & Commented Nov 14, 2018 at 13:32
  • @JeffSchaller Have added the full script and also without Veracrypt it does not stop executing. Commented Nov 14, 2018 at 13:34
  • I hate to insult your intelligence, but, … you say “it does not return to the console and [I] have to stop script execution with Ctrl + C …”  How do you know it hasn’t returned?  Have you run ps?  Have you typed “Enter”? See this. But, really, run ps and see what (if anything) is running in that terminal. Commented Nov 14, 2018 at 22:05

1 Answer 1

Reset to default
1

When you start a script with '< dot> < space> < script_name>' and you have in your script "exit", your window will be closed. The dot notation means you run it within the window and then the "exit" means to exit the window, not the script itself.
Try to add >/dev/null 2>&1 to each of the line (before final &) to find out which of the commands still holds stdout, eg.:
gnome-terminal --tab >/dev/null 2>&1 &
...
you may but need not to leave the exit at the end but it does not have any sense here. Run the script: ./startup.sh

Improve this answer
1
  • With >/dev/null 2>&1 it turned out that intellij AND the second shell script were responsible for the script not to terminate properly. Thanks! Commented Nov 14, 2018 at 15:03

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.