This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: inetd servers went wrong after upgrading cygwin


What is the `an "export" in the inetd list', please? More details are
appreciated.

BTW, I also tried setting a value under "...\Cygwin\Program Options" for
"c:\\cygwin\\usr\\sbin\\in.telnetd.exe", with no luck.

And I tried downgrading to Cygwin 1.3.9-1 and confirmed that without a
global environment variable CYGWIN inetd ran flawlessly under Cygwin
1.3.9-1. So it must be caused by some changes from Cygwin 1.3.9-1 to
1.3.10-1, as mentioned by Mr John Vincent. Sorry I cannot test with newer
Cygwin releases since they simply won't run, which is caused by some other
changes unknown to me.

Best regards,

Wu Yongwei

--- Original Message from Christopher Faylor ---

I haven't actually tried this with inetd.exe.  I've just verified that
setting a key for bash.exe has the desired effect.  I also tried the
"default" option (which is basically equivalent to setting the CYGWIN
environment variable everywhere) that works fine, too.

Maybe you are suffering from the fact that you are not including an
"export" in the inetd list.  You will need that if you want the values
to propagate.  Either that or you should just use "default" rather than
"c:\\cygwin\\usr\\sbin\\inetd.exe".

>[HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options]
>"C:\\cygwin\\usr\\sbin\\inetd.exe"="binmode ntsec tty"
>
>defined and it used to work.

cgf


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]