Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <3D20C9D8.98A2EB4D@ieee.org> Date: Mon, 01 Jul 2002 17:30:00 -0400 From: "Pierre A. Humblet" 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> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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. Pierre