in reply to Detachment problm

I guess I'm confused. The normal way to run a job every hour either on Unix or Windows is to setup a "cron" job, using cron or the Windows scheduler.

Unix cron Windows Task Scheduler On Windows to kill processes by name, taskkill /? will provide some help. On Unix pkill will do it. You know the name(s).

If you don't want that job to run again the next hour, then remove the cron job for it. Normally you shouldn't need your own process to sleep for an hour to start another process ( and since this process is replaced by the new running process, it is hard for me to understand how yet another one could be started). Let the OS run processes according the schedule. If you don't want it to run, remove it from the schedule. If you want to stop it while it is running, use some version of "kill". Yes, if you write a real "fork", if you die as the parent, the child dies too, but that seems overly complex. The exec() that you have now replaces your process with a new process with the same pid.

Replies are listed 'Best First'.
Re^2: Detachment problm
by baxy77bax (Deacon) on May 27, 2012 at 21:08 UTC
    ok i see you all did your homework and you know what is a standard approach. but that is not what i am looking for. so the whole project is a grid-wide and net-wide portable system. and i see that the time thing confused you . so let say that instead of time a user from a xy machine logs in and starts from main an application , but he doesn't want to wait for it to finish. plus this application is started on a computer on the other side of the globe(which is exactly what the app is doing). but then he decides to start 30 more applications on 30 different computers over the globe. and he doesn't want to wait for them to finish. but then a user get scared form some reason and decides to leave the main application. then it would be convenient to cover all his tracks so that all the pid's get terminated. that is why i was mentioning forks, exec and background jobs ,because it works in 90 percent of the time , but sometimes the forked and detached process stays detached when the main program is finished. i believe it is a bug in forking which is depended on OS (LINUX ONLY) so i'm looking for an advice

    cheers,