I have a file with permisson 711; but when an other user run the program, it can't open. This is the message:

/sbin/sh: ./myprogram: cannot open

Can any1 tell me why please?

Thanks!

That "myprogram" file must be a shell script. Shells need to read a file to execute it.

I have a file with permisson 711; but when an other user run the program, it can't open. This is the message:

/sbin/sh: ./myprogram: cannot open

Can any1 tell me why please?


Thanks!


#2 1 Day Ago
Perderabo
Unix Daemon Join Date: Aug 2001
Location: Rockville Md
Posts: 5,439

That "myprogram" file must be a shell script. Shells need to read a file to execute it.

Question:

Is this mean in the beginning of the program I have to have:


/sbin/sh

codes
codes
codes
.......

Thanks!

See our faq area for a discussion of the "#!" line and what happens without it. But to the shell, which is a program, a shell script is a data file. The only way a program can know what is in a data file is by reading the data file. There is no magic data that can be placed in a data file to change this fact.

Sorry to get in the middle. I'm trying to learn us much as I can from this forum, so I keep jumping from thread to thread (of course most of them don't make sense to me as I am a newbie)
I went to FAQ section, and read the thread (nice!), but I came up with one question regarding permissions: would it work if the script file had "read" permission but not "execute"? I'm sorry to make such questions, but I'm currently learning UNIX theoretical aspects, as I have limited access to the system.
Thanks,
panchopp.

Without execute permission, the kernel will refuse to execute it. It depends on the shell if you can do stuff like:
shell shellscript
However if the file is already open, the shell will no way to check. So this will work with read permission only with any shell:
shell < shellscript
I do that with one-time shellscripts...it saves a few keystrokes and makes it unlikey that I will accidentally rerun the script.

I see... good info, txs!