Programming

Dear Gurus,
I have encountered a C question, which I thought of sharing with you.
This question was asked by one of my technical training staff...Though my training was over I'm still thinking of a solution for this..

Write a C program to do a small task(lets say just simply printing a "Hello World" or so) such that the program should only give output or the desired result ony once after it got compiled and should never give the output nor do anything else. The program should not make use of files or any extrnal means of storing some data.

Please suggest me some ways of achieving this...

Regards
RK

You did not place any restrictions on what not to do. One way could be to remove yourself after the program execution.

Code:

[/tmp]$ cat try.cpp
#include <stdio.h>
#include <unistd.h>

int main (int argc, char* argv[])
{
    printf ("Bye Bye Cruel World :-( \n");
    return (unlink (argv[0]));
}
[/tmp]$ gcc -o try try.cpp -lstdc++
[/tmp]$ ls -l try
-rwxr-xr-x  1 xxxxxx g900 5202 May  9 02:51 try
[/tmp]$ ./try
Bye Bye Cruel World :-( 
[/tmp]$ ls -l try
ls: try: No such file or directory
[/tmp]$

Astounding that that works, vino! Looking at the Linux man page for unlink(2), I see that it does not detect "text busy". Compare that to the HP-UX man page for unlink(2). The Linux unlink(2) is rather permissive. If that man page is right, it even allows unlinking an active mount point! I'm not sure what effect that would have... Posix does not require that unlink(2) disallow unlinking mount points (but the text in the standard makes it clear that this is because Posix does not ever mention mount points). But unlinking an active program is another matter. On one hand, the Posix Standard says: That sounds to me like an OS is required to disallow the operation. But toward the end of the page we have: This leaves me confused as to whether or not the operation is allowed by Posix. But it will not work on most implementations of Unix. I would be interested if this program works with any kernel other than Linux.

A more portable solution would be have the program to write a little shell script to unlink the file and then exec that shell script.

I just tested on Solaris 10, t1000 server, seems to be working :

Does not work on HPUX 11i, as expected.

it works on RHEL3 !

It will work on any OS using a Linux kernel. This includes Red Hat. It is interesting that it works on Solaris though. I have always thought that ETXTBSY was silly. Of course you can't a program while it is running. But there is no reason to prohibit the unlink. The file will have zero links but will not be deleted until the reference count is also zero. This is the way data files have always been handled in Unix.