RE: Problem with 'cvs login'

["Rancier, Jeff" <Jeff dot Rancier at Sensis dot com>]

Although I still can't login with my login (I found an old .cvspass for
which I knew the password).  BTW can someone point me a utility to create
one which will work for CVS.  When I try to change my passwd for bash, via
passwd, it declares I'm not a valid user, although I'm in /etc/passwd).  I
removed the SYSTEMROOT entry from the passenv line in my
/etc/xinetd.d/cvspserver, recycled xinetd, and attempted an anonymous login
and it failed as before.  Changed it back, and it worked.  Here's the
screenshot:

,----
| jrancier@jrancier ~
| $ ps -ef
|      UID     PID    PPID TTY     STIME COMMAND
| jrancier    1388       1 con  19:53:15 /usr/bin/bash
| jrancier    1768    1388 con  19:53:52 /usr/bin/ps
| 
| jrancier@jrancier ~
| $ /usr/local/bin/xinetd.start
| 
| jrancier@jrancier ~
| $ cvs -d :pserver:anonymous@jrancier:/usr/local/cvsroot login
| Logging in to :pserver:anonymous@jrancier:2401/usr/local/cvsroot
| CVS password:
| cvs [login aborted]: reading from server: Software caused connection abort
| 
| jrancier@jrancier ~
| $ ps -ef
|      UID     PID    PPID TTY     STIME COMMAND
| jrancier    1388       1 con  19:53:15 /usr/bin/bash
|   SYSTEM     988       1   ?  19:53:59 /usr/sbin/xinetd
| jrancier    1628    1388 con  19:54:59 /usr/bin/ps
| 
| jrancier@jrancier ~
| $ kill 988
| 
| jrancier@jrancier ~
| $ /usr/local/bin/xinetd.start
| 
| jrancier@jrancier ~
| $ cvs -d :pserver:anonymous@jrancier:/usr/local/cvsroot login
| Logging in to :pserver:anonymous@jrancier:2401/usr/local/cvsroot
| CVS password:
| 
| jrancier@jrancier ~
| $
`----

Jeff

-----Original Message-----
From: Christopher Faylor [mailto:cgf-no-personal-reply-please@cygwin.com] 
Sent: Tuesday, April 26, 2005 7:06 PM
To: cygwin@cygwin.com
Subject: Re: Problem with 'cvs login'


On Tue, Apr 26, 2005 at 02:43:06PM -0700, Brian Dessent wrote:
>"Rancier, Jeff" wrote:
>
>> |    passenv     = PATH
>
>I don't know if this applies in your situation, but if xinetd is 
>stripping SYSTEMROOT from the child process' environment, then all 
>socket functions in that process will fail.  I think recent versions of 
>the cygwin1.dll have measures to prevent this from happening, but just 
>for grins try adding SYSTEMROOT to the above and see if it makes any 
>difference.

If that really does fix the problem then something is broken in CYGWIN.

Corinna fixed things so that this should no longer be a problem:

http://sources.redhat.com/ml/cygwin-announce/2004-11/msg00014.html

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/