Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Zeugswetter Andreas OSB sIT <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at>, Charlie Savage <cfis(at)savagexi(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED
Date: 2008-10-15 17:44:33
Message-ID: 48F62C01.40707@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Hmm. Now that you mention it, didn't we solve a similar problem by
> exploiting the behavior where CreateProcess creates a process but
> doesn't start it running? I'm envisioning
>
> * Create child process in suspended state
> * Assign it ownership of a lock (can we do that?)
> * Set it running
>

Not sure, but the SECURITY_ATTRIBUTES argument to CreateFile has a
bInheritHandle member that specifies whether a child process can inherit
the fiel HANDLE. I'm not sure if that would include locks on the file
HANDLE.

--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew T. O'Connor 2008-10-15 17:47:15 Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED
Previous Message Tom Lane 2008-10-15 17:43:49 Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED