averagejoe1
Programmer
To anyone that can help:
SCO Unix 5.05:
I am trying to keep a C program running after I log out. The login will start the C program via a shell script. I have 2 logins, 1 of the logins will do what I want - but the other will cause the C program to hangup after I logout (which I know is usually the case). Both logins are established using the Borne shell (i have checked the passwd table). Both logins belong to the same group and the permissions on the file are:
rwsrwxr-x
The owner of the file has been set to 'bin'.
I know I can do the following:
1) Run the C program with 'nohup'
2) Change my shell for both logins to ksh
3) Add the command setpgrp within the C program.
4) Have a signal catcher within the C program to disregard the hangup signal.
The first 3 work w/o any problems - haven't tried 4 yet - however my dilemna is why the 1 login will cause the program to hangup while the other won't.
I have checked profiles etc ... - I just feel that I am missing something very obvious somewhere. The only difference that I have found is that the login that is not working is starting the C program with 'exec' while that other isn't - however removing it does not work either.
Thanks for any help.
SCO Unix 5.05:
I am trying to keep a C program running after I log out. The login will start the C program via a shell script. I have 2 logins, 1 of the logins will do what I want - but the other will cause the C program to hangup after I logout (which I know is usually the case). Both logins are established using the Borne shell (i have checked the passwd table). Both logins belong to the same group and the permissions on the file are:
rwsrwxr-x
The owner of the file has been set to 'bin'.
I know I can do the following:
1) Run the C program with 'nohup'
2) Change my shell for both logins to ksh
3) Add the command setpgrp within the C program.
4) Have a signal catcher within the C program to disregard the hangup signal.
The first 3 work w/o any problems - haven't tried 4 yet - however my dilemna is why the 1 login will cause the program to hangup while the other won't.
I have checked profiles etc ... - I just feel that I am missing something very obvious somewhere. The only difference that I have found is that the login that is not working is starting the C program with 'exec' while that other isn't - however removing it does not work either.
Thanks for any help.