Programming

This doesn't work on HP-UX either - as expected, to be honest. Throws the same error.

Does that mean tested and worked on Solaris 10 ?
Or I mistook it has worked for tested instead ?

It worked.

Code:

# cc test.c
# ls -l a.out
-rwxr-xr-x   1 root     other       6988 May 11 13:18 a.out
# ./a.out
Hello, world... for now!
# ls -l a.out
-rwxr-xr-x   1 root     other       6988 May 11 13:18 a.out
# ./a.out
bash: ./a.out: cannot execute binary file

OK, If Solaris is allowing that, Solaris is broken. Unlinking an executable is one thing. But opening it for writing?? You've got to be kidding me. The Linux man page for open clearly states that this won't fly in even in Linux. When I saw that Solaris allowed unlinking a busy executable, I thought that the Solaris folks had made a reasoned change in the way things work. Now I see that they just fumbled. Don't write into running executables. A program like that is going to Solaris specific at best. And once Sun notices the problem they will probably fix it.

Do you mean its a possible bug in Solaris allowing to write in a executable that is currently being executed ?

If thats a bug, how would they be notified about the bug ?

Perhaps http://bugs.opensolaris.org/ ?

Well, it may be broken, but there is a ETXTBSY error documented in the Solaris open(2) manpage, and this is what it says:

Code:

ETXTBSY         The file is a pure procedure  (shared  text)
                     file  that  is  being  executed and oflag is
                     O_WRONLY or O_RDWR.

I don't really understand what a 'pure procedure' means, but it looks like that is the only thing that will fail to open for a write.