From: Ben Elliston <bje@redhat.com>
To: sid@sources.redhat.com
Subject: Testsuite patch
Date: Wed, 18 Jul 2001 18:55:00 -0000 [thread overview]
Message-ID: <20010719015505.B6B2E11197@scooby.brisbane.redhat.com> (raw)
I am about to commit the following patch. I would like to point out
that sid_stop has never have succeeded in closing the files associated
with spawned sid processes. The Expect documentation states that
"close -slave" only closes the slave end of a pty allocated by "spawn
-pty" (which is not applicable here).
I have been able to reduced file descriptor resource limits on Linux
with success. Solaris tests now work much better with their default
resource limits.
Ben
2001-07-19 Ben Elliston <bje@redhat.com>
* config/default.exp (sid_stop): Don't close with -slave.
*** default.exp 2001/07/13 15:19:13 1.2
--- default.exp 2001/07/19 01:50:35
***************
*** 107,113 ****
proc sid_stop {} {
global spawn_id
verbose "closing down sid" 2
! catch {close -slave}
catch {exec "kill" [exp_pid]}
wait
return 1
--- 107,113 ----
proc sid_stop {} {
global spawn_id
verbose "closing down sid" 2
! catch {close}
catch {exec "kill" [exp_pid]}
wait
return 1
next reply other threads:[~2001-07-18 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 18:55 Ben Elliston [this message]
2001-11-18 14:29 Ben Elliston
2001-12-10 2:32 ` Ben Elliston
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=20010719015505.B6B2E11197@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).