On Thu, Jan 07, 2010 at 02:08:12PM -0600, Wendigo Thompson wrote:

> Whoooah a lot of output from dtruss (I can't even pipe it to a file)

It writes to standard error, so you incant: "dtruss ... 2>file".

> so I'm not sure what you want me to do with that.  The output from
> postcat is (its a little anonymized, so if the IP addresses don't look
> right that's why):
> 
> *** ENVELOPE RECORDS /var/spool/postfix/maildrop/F423E1976D72 ***
> message_size:          444129             556               1
>      2          444129
> message_arrival_time: Fri Aug  1 15:23:30 2008
> create_time: Fri Aug  1 15:23:31 2008
> named_attribute: rewrite_context=remote
> sender:
> named_attribute: log_client_address=10.10.10.1
> named_attribute: log_message_origin=unknown[10.10.10.1]
> named_attribute: log_helo_name=10.10.10.10
> named_attribute: log_protocol_name=ESMTP
> named_attribute: client_name=unknown
> named_attribute: reverse_client_name=unknown
> named_attribute: client_address=10.10.10.10
> named_attribute: helo_name=10.10.10.10
> named_attribute: client_address_type=2
> named_attribute: notify_flags=1
> named_attribute: dsn_orig_rcpt=rfc822;my_delivery_mail...@my_system
> original_recipient: my_delivery_mail...@my_system
> done_recipient: my_delivery_mail...@my_system
> *** MESSAGE FILE END /var/spool/postfix/maildrop/F423E1976D72 ***

Yep, this message has no recipients. Perhaps cleanup(8) does not handle
these quite as gracefully as it should. It would be nice to see
that dtruss output, as we should be able to see the cleanup protoco
response to pickup.

It is a pity that MacOSX no longer provides a usable command-line
system call tracer. dtruss(1m) is still a toy, and can only be
used by root. If anyone can point me at a better CLI for tracing
processes with DTrace, I'd appreciate the pointer. Especially
if it allows non-root users to trace system calls in their own
processes, and has reasonably complete data structure decoding
for the usual set of system calls.

-- 
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.

Reply via email to