This is the mail archive of the
mailing list for the Cygwin project.
Re: CYGWIN and rlogin - non inheritance of variable CYGWIN
- From: arnaud GAND <arnaud dot gand at seti-ic dot com>
- To: CyberZombie <CyberZombie at mediaone dot net>
- Cc: cygwin at cygwin dot com
- Date: Thu, 13 Dec 2001 18:05:43 +0000
- Subject: Re: CYGWIN and rlogin - non inheritance of variable CYGWIN
- Organization: SETI
- References: <email@example.com> <3C18CD01.firstname.lastname@example.org> <3C18BB7A.email@example.com>
- Reply-to: arnaud dot gand at seti-ic dot com
> arnaud GAND wrote:
>> I fully apologize because my problem was that I did not restart my
>> computer. When reading the doc,
>> I understood "form start on" as "from start on bash". Sorry. I made
>> another tests with new system variables
>> and I found that these new system variables was not set in rlogin
>> So I reboot my NT4 station and now it's clear for me.I needed to
>> reboot first my
>> computer before testing rlogin.
>> Thank you very much, it helped me focused further on this weird
> One note about NT and above (not sure about Windows 9x/Me). If you
> set/modify variables in the system environment, you don't need to
> reboot to see the effects. Just restart the processes that need to
> see those variables. In this case, 'net stop inetd', 'net start
> inetd' should do...
Thank for the Hint but in these case it does not work. You need really
to reboot and stopping and starting inetd has no effect.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html