Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 13 Dec 2001 16:07:17 +0100
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: CYGWIN and rlogin - non inheritance of variable CYGWIN
Message-ID: <20011213160717.A740@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1008165892 DOT 14018 DOT ezmlm AT cygwin DOT com> <3C18CD01 DOT 2090105 AT seti-ic DOT com> <3C18BB7A DOT 70803 AT mediaone DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3C18BB7A.70803@mediaone.net>; from CyberZombie@mediaone.net on Thu, Dec 13, 2001 at 08:30:18AM -0600

On Thu, Dec 13, 2001 at 08:30:18AM -0600, CyberZombie wrote:
> 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 
> > session.
> > 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 
> > behaviour.
> >
> > Arnaud
> 
> 
> 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...

Unfortunately not.  inetd isn't started from nirvana but as a service
it's started as a child of the service control manager.  That means
it inherits its environment from the SCM which doesn't know about the
changed system environment apparently.

Basically you're right... but not for services.

So in this case only restarting windows or restarting the SCM (though
I don't know if that's at all possible) helps.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/