nullmail hiba!

Fri Dec 10 21:46:00 GMT 2004

Return-Path: <>
Received: from (unknown [])
	by (Postfix) with SMTP id B2C058776
	for <>; Fri, 10 Dec 2004 16:50:35 +0100 (CET)
Received: from (unknown [])
	by (Postfix) with ESMTP id 5E7DFDAF70
	for <>; Fri, 10 Dec 2004 16:28:55 +0100 (CET)
Received: from [] (
	by woody.fw.matav.intra with smtp (Exim 3.35 #1)
	id 1CcmgU-0006r0-00
	for; Fri, 10 Dec 2004 16:27:54 +0100
Received: (qmail 31561 invoked by alias); 10 Dec 2004 15:27:52 -0000
Mailing-List: contact; run by ezmlm
Precedence: bulk
List-Unsubscribe: <>
List-Subscribe: <>
List-Archive: <>
List-Post: <>
List-Help: <>, <>
Delivered-To: mailing list
Received: (qmail 31539 invoked from network); 10 Dec 2004 15:27:50 -0000
Received: from unknown (HELO (
  by with SMTP; 10 Dec 2004 15:27:50 -0000
Received: by (Postfix, from userid 201)
	id A5A291B401; Fri, 10 Dec 2004 10:28:37 -0500 (EST)
Date: Fri, 10 Dec 2004 10:28:37 -0500
From: Christopher Faylor <>
Subject: Re: need xterm to log to a file
Message-ID: <>
References: <> <>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.4.1i

On Fri, Dec 10, 2004 at 06:50:11AM -0500, Thomas Dickey wrote:
>On Thu, 9 Dec 2004, Al Goodman wrote:
>>On unix, xterm has an option that will enable it to log info typed and 
>>displayed to be logged to a file.  I downloaded the xterm source and 
>>compiled it.  When I enabled the option via Cntl-mouse-left-click the 
>>window hung.  Any suggestions on how to log input and output of an xterm 
>>would be appreciated.
>I see it's a (usually minor) error in xterm, which runs into a cygwin bug.
>The function creat_as() does a fork/wait, assuming that it has to strip 
>off the setuid/setgid privilges.  That's not needed in cygwin, but the
>fork/wait doesn't work (looks like a cygwin bug).  I'll add a fix in #198
>so it will work for cygwin.

How about saying "cygwin bug" a few more times?  I love it when people sling
that term around while providing no details.

If fork/wait didsn't work it would be a serious problem with repercussions
for every package in the cygwin distribution and it would certainly be
one that we'd want to fix.

Can you be more precise in detailing this problem?


More information about the Cygwin-xfree mailing list