From: Rick van Rein <rick@openfortress.nl>
To: Fabian.Kirsch@dlr.de
Cc: kzak@redhat.com, util-linux@vger.kernel.org, asbjorn@asbjorn.st
Subject: Re: script(1) plans
Date: Tue, 19 Mar 2019 08:53:03 +0100 [thread overview]
Message-ID: <5C909FDF.3040006@openfortress.nl> (raw)
In-Reply-To: <1552980724.5643.12.camel@dlr.de>
Hi Fabian,
> IMHO strace(1) needs an additional output format which is designed for
> further processing instead of eye-balls.
To that end, I've proposed an output option as a stream, by sending it as stdin to a command. I am still struggling with some crashes that I haven't been able to resolve yet (mostly lack of time). Is that the direction you are thinking in?
-Rick
prev parent reply other threads:[~2019-03-19 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 12:53 script(1) plans Karel Zak
2019-03-18 21:10 ` Martin Steigerwald
2019-03-19 7:30 ` Fabian.Kirsch
2019-03-19 7:53 ` Rick van Rein [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C909FDF.3040006@openfortress.nl \
--to=rick@openfortress.nl \
--cc=Fabian.Kirsch@dlr.de \
--cc=asbjorn@asbjorn.st \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).