Hi,
I was investigating a latency in a forking process on Solaris 10 and it
seems Dtrace itself aggravates the latency. The parent ignores SIGCHLD
and should return immediately, but was taking over a second. I suspect
similar behaviour is occurring with calls to execv.
On another machine running the same image, using Dtrace with the pid
provider caused the process to abort, along with some other pathological
behaviour that may also be related to unusual processing delays.
Can anyone shed light on any interaction between Dtrace (esp pid
provider) and process creation?
Also, can anyone suggest existing Dtrace scripts for monitoring process
families and creation/lifetimes?
Cheers,
Jono
--
------------------------------
This email, including any attachments, is only for the intended recipient.
It is subject to copyright, is confidential and may be the subject of legal
or other privilege, none of which is waived or lost by reason of this
transmission.
If you are not an intended recipient, you may not use, disseminate,
distribute or reproduce such email, any attachments, or any part thereof.
If you have received a message in error, please notify the sender
immediately and erase all copies of the message and any attachments.
Unfortunately, we cannot warrant that the email has not been altered or
corrupted during transmission nor can we guarantee that any email or any
attachments are free from computer viruses or other conditions which may
damage or interfere with recipient data, hardware or software. The
recipient relies upon its own procedures and assumes all risk of use and of
opening any attachments.
------------------------------
-------------------------------------------
dtrace-discuss
Archives: https://www.listbox.com/member/archive/184261/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184261/25769126-e243886f
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769126&id_secret=25769126-8d47a7b2
Powered by Listbox: http://www.listbox.com
