Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] [PATCHES] fork/exec patch

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>,"pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: [HACKERS] [PATCHES] fork/exec patch
Date: 2003-12-16 18:14:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32
>> As for Local System, most important services on win32 log on as Local
>> System by default.  Apache, mysql, etc. (I think, even SQL 
>server)  are
>> all configured to run this way, mostly because it causes less hassles
>> for the typical win32 user.  Of course, you can lock everything down
>> after installation.  Assumptions are just fundamentally different on
>> win32.
>initdb.c specifically avoids checking for running as root (or 
>administrator) on Windows. I assumed the service would run from a 
>privileged account.

That sounds reasonable, though. On Windows, you'd typically run initdb
whlie installing, from the account you installed with. But you run the
service under a service account.
You *could* log in as the service account, but that's now how it's
usually done..

>BTW, is anyone working on building in code to run as a 
>service? Or do we 
>plan to use a service wrapper?

I think custom code will be needed. It could be in the form of a wrapper
or in the form of integrated code. But if you use one of the general
wrappers, it's going to be hard to teach it to send signals to the
postmaster in the way we want (regardless of which method is chosen for

But it's probably best to just get it up and running on a command prompt
first :-)



pgsql-hackers-win32 by date

Next:From: Merlin MoncureDate: 2003-12-16 18:33:07
Subject: Re: [HACKERS] [PATCHES] fork/exec patch
Previous:From: Magnus HaganderDate: 2003-12-16 18:09:17
Subject: Re: [HACKERS] [PATCHES] fork/exec patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group