Mail Archives: cygwin/1999/12/14/23:46:42
Arrrggghhh! I should know better....
I had ^M's in my passwd file (binary mounts). I don't know how they got
there, but vim is "smart" enough not to show them; so I had no idea they
were present. Once I removed them, everything worked fine. It was not
necessary to use the 19991210 snapshot (I'm still using the 19991124
version). gdb helped me realize that it was "login.exe" that was failing
to execute "/bin/bash^M". Thanks, all, for the suggestions.
Now if only I could find that brown paper bag I keep for just these
sorts of emergencies...
--Chuck
Corinna Vinschen wrote:
>
> Chris Faylor wrote:
> >
> > On Tue, Dec 14, 1999 at 12:18:44AM -0500, Charles S. Wilson wrote:
> > >Has anybody been able to get telnetd working with the latest snapshots?
> >
> > FWIW, yes. I use telnet all of the time with the latest snapshots. I
> > don't have any of Corinna's stuff in my /etc/passwd, though.
> >
> > You should be able to debug this by running gdb on in.telnetd. There
> > is an option to in.telnetd to run it standalone. Possibly it's "-debug".
>
> I'm working with telnetd started via inetd as a service all the time.
> I'm using the ntsec option and the "U-" extension of /etc/passwd as
> well.
>
> I had problems with the first two or three snapshots after Chris
> signal handling patch. It might be related to another problem which
> I saw in tcsh but I don't know for sure.
>
> With the winsup-src-991210 snapshot, I have no problems in running
> inetd and telnetd again.
>
> Regards,
> Corinna
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -