| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Frank Featherlight <dirtydude(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Service not starting: Error 1053 |
| Date: | 2009-02-25 12:17:27 |
| Message-ID: | 49A536D7.3070907@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander wrote:
> Heikki Linnakangas wrote:
>>
>> Of course, none of this helps if the culprit is a DLL or a 3rd party
>> program that allocates the adress space immediately at CreateProcess.
>
> AFAIK all the cases where we *have* identified the culprit (which has
> been antivirus or firewall), this is exactly what it was doing...
Would it be possible to build a tool that runs through a series of
permission-checks, tries to grab some shared-memory, write to files in
the appropriate folders etc. and then shows the name of any process
interfering? Half the problem is that whenever someone has
Windows-related difficulties there's no standard tools we can use to
diagnose.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Featherlight | 2009-02-25 12:41:37 | Re: Service not starting: Error 1053 |
| Previous Message | Magnus Hagander | 2009-02-25 12:06:18 | Re: Service not starting: Error 1053 |