Mail Archives: cygwin/2002/07/07/22:48:29
On Mon, Jul 08, 2002 at 10:03:09AM +0800, Wu Yongwei wrote:
>So you do not define am environment variable CYGWIN, do you?
No, I do not. We were talking about the registry.
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".
>At least on this problem it seems I am not the only one affected. Mr
>John Vincent, as he said in his posting, had this problem too. My test
>shows clearly that after defining a CYGWIN environment variable with
>the value "binmode ntsec tty" and rebooting the computer the inetd
>works flawlessly. I have the registry key
>
>[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/
- Raw text -