Desktop Launcher of shell-script in gnome-terminal
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
which message don't make any sence for me,
because it appears, when the scipt doesn't exists, or i dont have the rights to execute the script or.....
2.2 When i found out, that this message:
"There was an error creating the child process for this terminal" appears, when i have no rights to execute a script,
i tried to create a Launcher with
Which started the Terminal, as i wanted,
showed the script output,
appended something like
"scanning for DEVICES, i will need a while for that , lalala"
At least i created a Launcher with
which was the correct way, and gave me my output in terminal.
Job: execute root command in terminal, showin it's output in terminal
1. create a shell script "scriptname.sh", which includes #! /bin/sh" in the row 1,
and all commands then, which you want to execute
2. make file executable with command "chmod a+x scriptname.sh"
3. set permissions of this script with "chmod 777 scriptname.sh"
4. create a launcher, pointing directrly to the script:
"sudo /home..../scriptname.sh" if root right are required for execution
Question to the Profis:
Is there a way to get better Error output in Linux?
If the System would clearly point out, that the problem is in the
missing scriptfile or missing rights,
this could be solved in 2 min, i needed 3 hours for that,
Linux will never rule the world, until the usability and clear user<->pc communication wont be present in it.
When you execute a command with gnome-terminal -e, all the output of that command goes to the newly created terminal. this is the point in launching something with gnome-terminal. Once the command has terminated, the gnome-terminal is closed. In your case, the error is displayed in gnome-terminal and the gnome-terminal is immediately terminated.
This is exactly what I expect from gnome-terminal. If you want to see the errors in your script, you should either redirect the output to somewhere or not launch it in a specifically created gnome-terminal or you should make sure your script does not stop after an error. The point of using gnome-terminal to launch your script is that all the output goes to that terminal.
Anyway, I understand how frustrating something must be when you don't understand it. I just spent 3 days trying to figure out why my damn SQL server didn't open the damn port on my Windows machine. It turns out the error was burried in the event dialog in the administrative stuff of system settings. Very very frustrating when you don't know where to look for an error and the system does not do what you expect it to do. I guess Windows will never rule the world either.