Re: serious problem in current CVS

2005-03-18 Thread Igor Pechtchanski
On Fri, 18 Mar 2005, Yitzchak Scott-Thoennes wrote: > On Fri, Mar 18, 2005 at 03:32:24PM -0500, Christopher Faylor wrote: > > On Fri, Mar 18, 2005 at 02:51:52PM -0500, Joe Buehler wrote: > > >In case this is not already known, the current CVS has a serious > > >problem -- attempts to rsh or ssh in

Re: serious problem in current CVS

2005-03-18 Thread Yitzchak Scott-Thoennes
On Fri, Mar 18, 2005 at 03:32:24PM -0500, Christopher Faylor wrote: > On Fri, Mar 18, 2005 at 02:51:52PM -0500, Joe Buehler wrote: > >In case this is not already known, the current CVS has a serious > >problem -- attempts to rsh or ssh in to a machine running a cygwin1.dll > >compiled from it fail

RE: serious problem in current CVS

2005-03-18 Thread Richard Campbell
> In case this is not already known, the current CVS has a serious problem -- attempts to rsh or > ssh in to a machine running a cygwin1.dll compiled from it fail with an error message regarding > a failed setgid() call. If the user logging into the machine is listed in /etc/passwd with a primar

Re: serious problem in current CVS

2005-03-18 Thread Christopher Faylor
On Fri, Mar 18, 2005 at 02:51:52PM -0500, Joe Buehler wrote: >In case this is not already known, the current CVS has a serious >problem -- attempts to rsh or ssh in to a machine running a cygwin1.dll >compiled from it fail with an error message regarding a failed setgid() >call. WJFFM. cgf -- Un

Re: serious problem in current CVS

2005-03-18 Thread Joe Buehler
Igor Pechtchanski wrote: How current is "current"? FWIW, I can't reproduce it with self-built DLL from CVS two days ago: It's current as of an hour or so ago. I had a similar problem with CVS a couple days ago and had put it down to in-progress changes. The 1.3.15-1 source does not have the probl

Re: serious problem in current CVS

2005-03-18 Thread Igor Pechtchanski
On Fri, 18 Mar 2005, Joe Buehler wrote: > In case this is not already known, the current CVS > has a serious problem -- attempts to rsh or ssh in > to a machine running a cygwin1.dll compiled from it > fail with an error message regarding a failed setgid() > call. How current is "current"? FWIW,