search for: sigtimedwait

...though the child has exited. In this situation, the child is clearly visible as a zombie; we have also seen the situation where there is no zombie child. I've not been able to reproduce this situation. I think that the correct way to fix this would probably be to use something like SIGIO and sigtimedwait() rather than select(), but that would be a substantial change. A simple fix for this problem would be to set a maximum timeout on the select() call of e.g. 15s. Are there any complications or bugs that could be introduced by such a change? Paul

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything

I''m trying to do some userspace tracing on a server-process with the pid provider. My problem is, that the only probes the pid-provider lists for the server-process (to which I attach dtrace with "-p nnnn") are coming from "ld.so.1". There''s not a single one from my modules. If I''m specifying "a.out" (or any of our shared-objects) as the

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org