From: Karel Zak <kzak@redhat.com>
To: Robert Urban <urban@unix-beratung.de>
Cc: util-linux@vger.kernel.org
Subject: Re: Feature request: write out buffer to typescript on SIGTERM
Date: Tue, 28 Jul 2015 10:39:32 +0200 [thread overview]
Message-ID: <20150728083932.GG6865@ws.net.home> (raw)
In-Reply-To: <55B6B370.5020602@unix-beratung.de>
On Tue, Jul 28, 2015 at 12:40:48AM +0200, Robert Urban wrote:
> is there a good reason why script does not flush it's typescript buffer when it
> gets a signal such as SIGTERM?
Not sure if you're talking about the current script(1) in git tree
(it's a new version) or about the original version.
I have improved sensitivity to the SIG{TERM,INT,QUIT}, now it properly
terminates the session and close the files. Previously it called
abort() (the version in git).
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-07-28 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 22:40 Feature request: write out buffer to typescript on SIGTERM Robert Urban
2015-07-28 8:39 ` Karel Zak [this message]
2015-07-28 19:37 ` Robert Urban
2015-07-28 23:49 ` Karel Zak
2015-07-29 0:02 ` Robert Urban
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=20150728083932.GG6865@ws.net.home \
--to=kzak@redhat.com \
--cc=urban@unix-beratung.de \
--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