Good luck...
Whatever the reason, the csh does seem to solve the problem for me at the present time.
On May 2, 2005, at 6:09 PM, Sean Kamath wrote:
The Borne shell doesn't do job control. No "nohup" command will insulate against SIGTERM, it only protects against SIGHUP (hence the name). I'm completely confused why the sh would send a TERM to the processess.
It could be that the processes are sending a request to go in the background (SIGSTOP) and the sh is terminating them instead. I'll see if I can duplicate the behaviour and see what's causing this problem, but it sounds like you have a workaround.
Sean
________________________________________________________
Dr. Robert Young ALI Database Consultants 1151 Williams Dr Aiken SC 29803 USA
WWW: http://www.aliconsultants.com
Tele: 1-803-648-5931
Toll free in US: 1-866-257-8970 Fax:1-803-641-0345
Email: [EMAIL PROTECTED]
"Source of Rdb Controller, software for database analysis & performance tuning"
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
