Hi Alastair,
by now I discovered, how to do without the sticky bit. So this is no longer a
problem for me. I just don't understand it and possibly other users may come
accross the same problem.
> I've no idea what's happening here - my experience of the sticky bit is
> pretty much limited to following instructions in documentation
> and security alerts.
>
> Some questions:
>
> Isn't the "sticky bit" also known as the "set user id bit".
I thought that the "sticky bit" and the "set user id bit" are the same as well.
To express myself clearly: I did "chmod 4755 Test.hs" so that the script is
always executed under my rights.
> Which user are you running as?
chitil
> Which user owns the script?
> Which user owns runhugs?
> What are the permissions on runhugs and on the script?
-rwsr-xr-x 1 chitil info2 202 Apr 24 10:28 Test.hs
lrwxrwxrwx 1 install info2 35 Jan 28 20:12 /usr/local/bin/runhugs ->
/usr/local/lib/hugs/1.4/bin/runhugs
-rwxr-xr-x 1 install info2 487284 Mar 17 18:19
/usr/local/lib/hugs/1.4/bin/runhugs
Then just do "chmod 755 Test.hs" and the script runs perfectly.
> ps If you always get bad error messages from runhugs, it might be that
> your system doesn't support snprintf and vsnprintf
You are right, configure says
checking for vsnprintf... (cached) no
checking for _vsnprintf... (cached) no
checking for snprintf... (cached) no
checking for _snprintf... (cached) no
Neither SunOS 5.5 nor SunOS 5.6 support it. Well, so I will have to do without
error messages.
Thank you for your help,
Olaf
--
OLAF CHITIL, Lehrstuhl fuer Informatik II, RWTH Aachen, 52056 Aachen, Germany
Tel: (+49/0)241/80-21212; Fax: (+49/0)241/8888-217
URL: http://www-i2.informatik.rwth-aachen.de/~chitil/
