> > So, if I want to have multiple servers registered, I could do:
> > postgres /regserver MyPGServer_1 -D c:/data1
> > postgres /regserver MyPGServer_2 -D c:/data2
> > and so on.
>
> Where do you plan to store this data, if not in the registry?
Um, well, of course implicitly, but only as an artifact of the CreateService
call. Basically, all I see that need to be done is to, when calling
CreateService, augment the lpBinaryPathName argument with the argument list
specified.
Any objections?
But, when the discussion starts degenerating into the finer points of
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Foo\Blah vs other
esoteric register keys, well, that just seems misguided.
> Can *all* env variable settings be set on the commandline as well?
Haven't needed any so far. There might well be, but then I think any
subsequent discussion should really be centered around providing command
line args for these too, right?
> If so, we can just use a single registry key to store a commandline for
the service.
Yeah, by letting the Win32 Service API handle the details, as above. End of
story.
Cheers,
Claudio
---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>
