| From: | Ronald Kuczek <kuczek(at)kuczek(dot)pl> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers-win32(at)postgresql(dot)org |
| Subject: | Re: registry vs. environment (was re:binary |
| Date: | 2004-02-12 18:37:24 |
| Message-ID: | 402BC7E4.3010502@kuczek.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
Użytkownik Bruce Momjian wrote:
>I assumed all environment variables would be exported to the process.
>The problem is allowing environment variables to override registry
>settings.
>
>One idea would be to do both --- if an environment variable isn't set,
>get the value from the registry and set the envronment variable. If the
>environment variable is set, use that instead of the registry --- that
>might be the best of both worlds.
>
>
Enviroment variables are stored in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment.
There is no problem to look there if any variable is set or not and - to
add a registry key with new variable or to modify existing.
Rony
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2004-02-12 18:38:52 | Re: registry vs. environment (was re:binary installer) |
| Previous Message | Bruce Momjian | 2004-02-12 17:47:11 | Re: registry vs. environment (was re:binary |