It was about three o'clock on a Thursday afternoon when Kevin
called me. I remember the time because I had just been thinking
about knocking off early. It had been a hard week, and the P&L
was looking good, so I was ready for a break. Then my cell phone
chimed, and when I pushed "Talk", Kevin's voice was in my ear.
Kevin doesn't call me all that often. We hardly ever see each
other socially any more- he's in Seattle, I'm here on the East
Coast. He's a Filepro and C kind of guy, neither of which I do much
with any more. We keep in touch; Xmas cards and all that, but only
chat now and then, and usually it's just that: chit chat.
But today Kevin had a problem. "I've got this script that keeps
looping on itself and I can't figure out why".
Well, I knew better than to ask the obvious- Kevin is no fool:
the script wouldn't be calling itself. But I also knew that Kevin
was doing more and more Linux, so I asked "What OS?". The answer
came across the country on fiber optic cables and was then
broadcast for my cell phone to pick up: "Red Hat 6.1, patched to
I thought for a second and said "Let's just try something- this
isn't your answer, but just humor me. Put "#!/bin/sh" at the top of
Kevin paused before he answered. He knows I'm not an idiot, but
sometimes he wonders.. "Umm, sh is a link to bash on Linux", he
"I know", I explained, "but just do it anyway. Try it.". I heard
keys clicking, and then his voice came back. "Son of a gun- it
doesn't loop- I don't get it. What's going on?".
It was my turn to pause. "Well, I have another question, though
it's really more of a statement: you have this script run when you
log in, don't you?".
"That's the problem. You've done that wrong, and that's why it
Do you know what Kevin did wrong and why the "#!bin/sh" stopped
If this page was useful to you, please help others find it:
More Articles by Tony Lawrence
- Find me on Google+
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Jump to Comments
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.