Mail Archives: cygwin-developers/2002/07/01/17:30:45

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 17:30:00 -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> <3D20C1DA DOT 26509E01 AT ieee DOT org> <20020701212139 DOT GE25306 AT redhat DOT com>

Christopher Faylor wrote:

> >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).
> That probably explains what's happening then.  Harold Hunt just posted an
> strace.  Does this make sense?

I assume the process isn't privileged.
As the uid and gid don't change (if I understand), the line
  385 5428879 [main] xterm 1536 seteuid32: Process token not verified
is abnormal. I am downloading xfree and will look into it.


- Raw text -

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