| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: win32 service code |
| Date: | 2004-05-27 21:12:15 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE34BB51@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
>> > >I had a thought that on win32 pg_ctl start/stop would
>mean start/stop
>> > >the service (always) on win32, and for this to be the only way to
>> start
>>
>> > No, we need to be able to run *not* under the service manager, and
>> > pg_ctl needs to be able to control that, IMNSHO.
>> >
>> > Users might not have admin privs (e.g. in a classroom setting).
>>
>> Ok, fair enough. Do you think start/stop service should
>still be done
>> through pg_ctl?
>
>What are the advantages of _not_ using pg_ctl?
That all other services are handled through the service MMC snapin.
That's not a reason not to support *both*, though.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-05-27 21:14:47 | Re: win32 service code |
| Previous Message | Bruce Momjian | 2004-05-27 21:06:08 | Re: win32 service code |