comment on

Without more data it's going to be hard to guess what's happening in that case. Here's an SSCCE which might help:

cd /tmp
cat > foo.sh <<EOT
#!/bin/sh
echo Relative path
./bar.sh
echo Absolute path
/tmp/bar.sh
echo No path
bar.sh
EOT
cat > bar.sh <<EOT
#!/bin/sh
echo bar running as \$0
EOT
chmod 0755 foo.sh bar.sh
sudo chown root bar.sh
sudo cp -p bar.sh /usr/local/bin
./foo.sh
[download]

Running this locally (not on Solaris!) gives this expected output:

Relative path
bar running as ./bar.sh
Absolute path
bar running as /tmp/bar.sh
No path
bar running as /usr/local/bin/bar.sh
[download]

If you see the same, then you'll need to determine what's different about functions.sh and compile.sh compared to foo.sh and bar.sh. Don't forget to remove bar.sh from /usr/local/bin when you're done. Good luck.

In reply to Re^3: OT: invoking shell script with relative path and absolute path by hippo
in thread OP: invoking shell script with relative path and absolute path by vinoth.ree

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks