UNIX for Dummies Questions & Answers

Hi,

I have written a shell script for automating some of our repetitive activities. I want all my colleagues to use my script and do the activities automatically by just running the script.

But I do not want them to see the code. Is there a way we can generate something like an executable from the script, so that they have access only to the executable and they cannot see the source code.

I do not want to give just the execute permission. If I do that then I need to store the script in one common place. Since the script needs to be run in many servers then I need to copy the script in all the servers which is duplication and maintanence is difficult and every body will try to change the script.

Instead, I want to generate an executable and give that to my colleagues so that they can run it wherever they want and I alone can maintain the source code.

I am using HP-UX 11.11

thanks in advance for your help.

may be you should try

shc - shell script compiler

I have been using shc compiler from long time, now I am moving to another version or different OS where it is not working as expected.

I have shc working pretty well in Solaris 8 , On Solaris 10, I am unable to make/compile shc

make shc on Solaris 10 :

$ make shc
gcc -Wall -O6 -pedantic shc.c -o shc
In file included from /usr/include/sys/signal.h:34,
from /usr/include/signal.h:26,
from shc.c:94:
/usr/include/sys/siginfo.h:259: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:292: error: parse error before '}' token
/usr/include/sys/siginfo.h:292: error: ISO C forbids data definition with no type or storage class
/usr/include/sys/siginfo.h:294: error: parse error before '}' token
/usr/include/sys/siginfo.h:294: error: ISO C forbids data definition with no type or storage class
/usr/include/sys/siginfo.h:390: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:392: error: conflicting types for `__proc'
/usr/include/sys/siginfo.h:261: error: previous declaration of `__proc'
/usr/include/sys/siginfo.h:398: error: conflicting types for `__fault'
/usr/include/sys/siginfo.h:267: error: previous declaration of `__fault'
/usr/include/sys/siginfo.h:404: error: conflicting types for `__file'
/usr/include/sys/siginfo.h:273: error: previous declaration of `__file'
/usr/include/sys/siginfo.h:420: error: conflicting types for `__prof'
/usr/include/sys/siginfo.h:287: error: previous declaration of `__prof'
/usr/include/sys/siginfo.h:424: error: conflicting types for `__rctl'
/usr/include/sys/siginfo.h:291: error: previous declaration of `__rctl'
/usr/include/sys/siginfo.h:426: error: parse error before '}' token
/usr/include/sys/siginfo.h:426: error: ISO C forbids data definition with no type or storage class
/usr/include/sys/siginfo.h:428: error: parse error before '}' token
/usr/include/sys/siginfo.h:428: error: ISO C forbids data definition with no type or storage class
/usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
/usr/include/sys/siginfo.h:437: error: parse error before '}' token
/usr/include/sys/siginfo.h:437: error: ISO C forbids data definition with no type or storage class
In file included from /usr/include/signal.h:26,
from shc.c:94:
/usr/include/sys/signal.h:85: error: parse error before "siginfo_t"
In file included from shc.c:94:
/usr/include/signal.h:111: error: parse error before "siginfo_t"
/usr/include/signal.h:113: error: parse error before "siginfo_t"
*** Error code 1
make: Fatal error: Command failed for target `shc'

The other issue which is not compile issue is on Linux Platform ( Red Hat 2.6 kernel 2.6.9-55.0.2.ELsmp)

I am able to compile shc and comiple my shell scripts using shc without any issues. When my script is running and I do
ps -ef |grep myscript

It is kind of showing whole script in Linux ( That is defeating purpose using shell script compile)

I have tried to contact author few times as well but could not contact so not sure whether his email id got changed.

Any help is greatly appreciated.

Scripts are supposed to be simple and readable.
Why not rewrite it in C?

Then your problem is one of "change management", and in this simple case can be solved by making the script readable but not writeable.

If people are making extra copies and changing those, that is not your problem, surely?

If you know well how to code in C.
What about solving & giving suggestions on how to solve this particular issue vs why you need this ?

Finally found the solution for issue
Driver Development - where is ctid_t defined? (Solaris 10)
The fix is to build a fresh set of gcc "fixed" headers:

# cd /opt/sfw/gcc-3/lib/gcc-lib/i386-pc-solaris2.9/3.3.2/install-tools/

# cat > mkheaders.conf
SHELL=/bin/sh
SYSTEM_HEADER_DIR="/usr/include"
OTHER_FIXINCLUDES_DIRS=""
FIXPROTO_DEFINES="-D_XOPEN_SOURCE"
STMP_FIXPROTO="stmp-fixproto"
STMP_FIXINC="stmp-fixinc"
^D

# ./mkheaders