Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: win32 service code
- 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: Thu, 27 May 2004 23:12:15 +0200
- Message-id: <6BCB9D8A16AC4241919521715F4D8BCE34BB51(at)algol(dot)sollentuna(dot)se>
>> > >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
- Follow-Ups:
- Re: win32 service code
- From: Andrew Dunstan
- Re: win32 service code
- Prev by Date: Re: win32 service code
- Next by Date: Re: win32 service code
- Previous by thread: Re: win32 service code
- Next by thread: Re: win32 service code
- Indexes: