DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 56A5B3861838
MIME-Version: 1.0
References: <vriuwnwznjj7.fsf@gavenkoa.example.com>
 <vriu5z4cpd84.fsf@gavenkoa.example.com>
In-Reply-To: <vriu5z4cpd84.fsf@gavenkoa.example.com>
From: Bill Stewart <bstewart@iname.com>
Date: Mon, 4 Jan 2021 15:39:20 -0700
Message-ID: <CANV9t=QXiTVAYp=us72vmTOqf0LuTCRnzG4_Yc_Oa-SYUgjFNQ@mail.gmail.com>
Subject: Re: Setting env var CYGWIN for Cygwin service?
To: cygwin@cygwin.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

On Mon, Jan 4, 2021 at 3:08 PM Oleksandr Gavenko wrote:

> /usr/bin/exim-config has line with:
>
>   cygrunsrv -I exim -p /usr/bin/exim -e CYGWIN="${cygenv}" ...
>
> So it is the answer (as pointed by others).
>
> Still "procexp" doesn't show anything else besides PATH/WINDIR for "exim"
> process. It can be that cygrunsrv passed env vars in some Cygwin *magical way*.
>
> Cannot confirm this, attempt to read /proc/X/environ gives "<defunct>". There
> is no problem to read "environ" for other Cygwin processes.

I have observed the same thing. The environment variable setting
exists in the HKLM\System\CurrentControlSet\Services\<servicename>\Parameters\Environment
registry subkey, but Process Explorer does not show the environment
variable in the list of environment variables for the process.

I have not looked at the code, but it seems that environment variables
specified in this way are not propagated to the environment block for
the process but instead are read some other way.

Bill
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple