Mail Archives: cygwin-developers/2002/07/01/16:56:41

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <>
Date: Mon, 01 Jul 2002 16:55:54 -0400
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: Any ideas with xterm/xfree problem?
References: <20020701204140 DOT GA25217 AT redhat DOT com>

Christopher Faylor wrote:
> Is anyone reading the discussion in cygwin-xfree?  If so, I was
> wondering if you had any idea what was causing the problem.

I assume you mean
Is there any other info?

> Out of curiousity, would adding something like:
>   if (myself->uid == uid)
>     return 0;
> to the top of seteuid32 be "wrong"?  It seems like xterm is just
> calling setuid with its own uid.  So, this test would short circuit
> that.

It used to be that way, but then a new token wasn't created when
the gid changed and the uid didn't (in cygwin gid changes are not
really effective until the next setuid).

> I don't know what would be failing, otherwise to cause this problem.
> cgf


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019