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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The "#!"sign in the first line first character in a file is a special character, wich is intended to give shell tips about the archive.
When you put "#! /bin/bash" you are telling shell to execute this file with bash, wich is a shell of coarse, or virtual shell wich mimics shell in graphical environ.
"#! /usr/bin/env bash" do the same but thru env utility.
Scripting file cannot have those lines, but it can cause troubles or unexpected behavior in certain cases.
In python scripting one can put "#! /usr/bin/env python" so the shell won't try to execute this file sending it for python interpreter.
The option -x in this case make bash more verbose, printing aliases and many stuffs in the prompt.
That does help with the #! issue, i assumed something like that, but i wasnt sure.
but my -x issue is still there, maybe it would help if copied the script im trying to run.
Code:
#!/bin/bash -x
echo -n "Enter some text > "
if read -st 2;
then
echo "Your wrote: $REPLY"
else
echo "To slow suckah"
fi
the script works. but as far as i know, using the -x should trace through the script, which is not what im getting when i run the script.
ive tried using -x on other more complicated scripts and still, i can detect no change in the operation.
im running debian if that has anything to do with anything.
thanks for the help everyone, i will be playing with ltrace and strace tonight, as armandrix mentioned.
but, for the record, i did figure out what my problem was.
ive been running the scripts via the bash command, like so:
Code:
odimachkie@LinuxBox:~/bin$bash myscript.sh
the reason i was doing this was that just typing the filename was not working as it would with other scripts. this is because the file permissions did not allow for execution. a little chmod 755 did the trick and now -x works like a dream.
i'm very obviously new at this, so thanks for the input everyone. every little bit helps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.