[SOLVED] Running Bash script - Output can't be seen because command window closes

pizzipie · 09-25-2017, 01:58 PM

I have a bash script that when run the output scrolls by really fast and then the command window closes. You can't see the output.

What would cause this? How to fix?

Code:

echo "======================="
echo 
echo "-- START --"
echo
pwd
#exit
# bash	SET is a bash command - allows you to change the values of shell options
# bash -z file attribute check to see if permissions are ok
# bash $1 positional parameter

echo "SET autocommit=0;SET unique_checks=0;SET foreign_key_checks=0;" > tmp_sqlhead.sql
echo "SET autocommit=1;SET unique_checks=1;SET foreign_key_checks=1;" > tmp_sqlend.sql

if [ -z "$1" ]		# $1 is command line parameter ie: 'accounts' or 'polly' etc.
  then
    echo "-- Dumping all DB ..."
    echo
    for I in $(mysql -urick -prick -e 'show databases' -s --skip-column-names); 
    do
      if [ "$I" = information_schema ] || [ "$I" =  mysql ] || [ "$I" =  phpmyadmin ] || [ "$I" =  performance_schema ] 
      	then
         	echo "-- Skip $I ..."   # exclude these DB's
       	continue
      fi
       d=$(date +%Y%b%d-%T_)	# get current date and time
       echo "-- Dumping ""$d""$I ..."
   	    mysqldump -urick -prick --add-drop-database --databases $I | cat tmp_sqlhead.sql - tmp_sqlend.sql  | gzip -fc > "/home/rick/DB-Web/mydb-bakup-folder/"$d"$I.sql.gz" 
    done
else			# ========  process single file from command line parameter  ============
      I=$1;
      d=$(date +%Y%b%d-%T_)
      echo "-- Dumping ""$d""$I ..."
		mysqldump -urick -prick --add-drop-database --databases $I | cat tmp_sqlhead.sql - tmp_sqlend.sql  | gzip -fc > "/home/rick/DB-Web/mydb-bakup-folder/"$d"$I.sql.gz"   
 fi

# remove tmp files

rm tmp_sqlhead.sql
rm tmp_sqlend.sql

echo
echo "-- FINISH --"

rknichols · 09-25-2017, 03:28 PM

Just add at the bottom of the script:

Code:

read -t 20 || exit
read -p "Press <enter> again to close   "

The script won't terminate until the first read times out in 20 seconds. If you press <enter> during that time, then the second read will wait forever for another <enter>.

pizzipie · 09-25-2017, 07:50 PM

Thanks rknichols,

Why is this script doing this. Most of the ones I write don't present this sort of behavior.

See this script which acts normally.

Code:

 #!/bin/bash 
  #Sun 24 Sep 2017 18:23:28 
  
  # This is the companion script to mydb-mysqldump.sh
  # mydb-mysqlrestore.sh  will restore the files dumped by that program
  
  #File: DB-Web/mydb-mysqlrestore.sh
  
folder="/home/rick/DB-Web/mydb-bakup-folder"

# if gzip files unzip them
find "$folder" -type f -iname '*gz' -exec gunzip {} + 

   echo "-- Start"
   echo
   echo -- Restoring --
   echo
    
    for I in $(ls -d "$folder"/* ) 
    	do
    	   echo "$I" | awk -F_ '{print $2}' 	 
    		mysql -urick -prick < $I 
		done


echo

    	
echo "-- Finish"

rknichols · 09-25-2017, 08:27 PM

What matters is how the script is invoked. If either script is run from an existing command window, then that window will remain open when the script exits and returns control to that command shell**. But, if you launch the script from a menu or a desktop launcher configured as "Run application in a terminal", then there is no shell to return to and the window will close immediately when the script exits. The commands I suggested provide a way to keep such a terminal window open.

** If the command you type is "exec path/to/script", then the invoking shell is overlaid by the one running the script and the window will close immediately upon termination.

pizzipie · 09-25-2017, 09:17 PM

Is there a way to not have the 'baby' command window to show the output of a script run through the launcher.

If I can't get the regular display to show output is there a way to change font etc from the 'baby' window. See attachment for what I'm talking about. you have to use a magnifying glass to read Enter Password:

pan64 · 09-26-2017, 12:56 AM

I have no idea what do you mean by baby window. You can redirect the output of your shell script into file and use a text editor to check the content (of that file).

ondoho · 09-26-2017, 01:07 AM

how are you invoking the script(s)?

pizzipie · 09-26-2017, 02:37 PM

Quote:

how are you invoking the script(s)?

I am using a launcher as attached.

suicidaleggroll · 09-26-2017, 03:06 PM

Quote:

Originally Posted by pizzipie

Is there a way to not have the 'baby' command window to show the output of a script run through the launcher.

If I can't get the regular display to show output is there a way to change font etc from the 'baby' window. See attachment for what I'm talking about. you have to use a magnifying glass to read Enter Password:

It's just using the default terminal. Open the default terminal yourself, change the default font, and that should change it for your script.

pizzipie · 09-26-2017, 08:19 PM

Quote:

It's just using the default terminal. Open the default terminal yourself, change the default font, and that should change it for your script.

The default terminal has a white background with black text and a menu with a number of options. The one that shows up when you use the launcher has a black background with white text and a minimal menu where all you can do is change the size a little bit.

We're talking two different animals here.

R

Ratamahatta · 09-27-2017, 05:36 AM

Seems like you have more than one terminal emulater (i.e. "animal"

) installed on your system.

Open a terminal and before and when that problematic script is running enter:

Code:

ps ax

Then compare the outputs. There should be two lines more in the second output. One is the script and one is the terminal emulator used for that script. Then you may be able to start that other terminal emulator (because now you know it's name) and change it's settings.

Another way might be changing the default terminal emulator. On my Debian based system the link is /etc/alternatives/x-terminal-emulator. Should be similar on Ubuntu. Do (assuming the path is the same):

Code:

ls -l /etc/alternatives/x-terminal-emulator

to see what it points to and compare it to the name of your usual terminal emulator.

pizzipie · 09-29-2017, 11:14 AM

A picture is worth a thousand words eh?

Apparently I can't explain myself properly.

R.

rknichols · 09-29-2017, 12:36 PM

That launcher is not creating that window itself. Something in the script is doing that.

ondoho · 09-29-2017, 02:33 PM

your op says "output can't be seen because command window closes" but now we can see it.
so, we moved on to the next problem, which is too small font?
you can either edit the script, or, since this is clearly xterm in the scrot, you can make a quick web search on how to change xterm's font size. it can even use ttf/otf fonts.

pizzipie · 09-29-2017, 04:39 PM

I apologize to all for mixing up two different threads.

The most recent answers from rknichols and ondoho got me thinking along a different path.

The answer is contained in this link: https://ubuntu-mate.community/t/laun...-terminal/4918

Specifically:

Quote:

MY SOLUTION

There's many solutions, including forgetting the "Application in Terminal" altogether and just run mate-terminal with the -e option but I wanted to have my cake and eat it, too. And it's a one-time command:

Code:

sudo ln /usr/bin/mate-terminal /usr/bin/gnome-terminal

I hope this helps someone else who has a similar problem.

R