Since the process didn't exit, it must still be in the process table. When you get to this state have your process do something like: fprintf(stderr, "The weird process is pid %d\n",pid); fflush(stderr); sleep(1000);
Then see what ps says about that process. If that doesn't offer any hints, attach to the process with gdb, vdb, wdb, dde or some other debugger. My HP-UX system doesn't have a signal 64, either. On Thu, 30 May 2002, Charles F. Fisher wrote: > On Thu, May 30, 2002 at 11:53:34AM -0400, Paul Haas wrote: > Much stuff snipped.. > > The EINTR case doesn't make sense with WNOHANG, but HP-UX doesn't always > > do things that make sense. If you get the "Now what should I do?" > > message, then add code to check WIFSIGNALED(), WIFSTOPPED() and > > WIFCONTINUED() and do something appropriate. If you reach the perror(), > > hopefully the text there will offer some clues. > > > > I don't have an HP-UX 11.11 system, I'm looking at the manpages on > > an HP-UX 11.00 system. > > > Thank you for the code snippit - checking WIFSIGNALED() showed a non-zero > result, WTERMSIG() returned 64, which isn't in /usr/include/sys/signal.h. > In any case WIFEXITED() was returning 0, so WEXITSTATUS was returning garbage. > Any idea was signal 64 would be? It's being returned consistently; if it's > a normal termination signal I'll fix the routine to treat it as such. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html