mspaper writes: > What can cause the child to receive SIGHUP? A process normally receives SIGHUP when a "modem disconnect" is detected on the controlling tty. See termio(7I).
It's possible for other processes to send SIGHUP using the kill(2) system call. You can diagnose what's going on using the truss and dtrace facilities. Both will reveal details about the sender. > Once the system command fails due to this error, it cannot recover till the > application is restarted You'll likely need to do some debugging on the application and find out why it's not working properly. It sounds quite a bit like you're encountering some generic UNIX programming problems, and not things that are specific to Solaris. But do publish complete source for an example program showing the problem if you can. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
