Re: [Patch] - Fix for bug #2558, InitDB failed to run

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [Patch] - Fix for bug #2558, InitDB failed to run
Date: 2006-08-15 14:43:50
Message-ID: 44E1DDA6.5030306@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian wrote:
> Andreas Pflug wrote:
>> Tom Lane wrote:
>>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>>
>>>> I am more than somewhat perplexed as to why the NUL device should be a
>>>> security risk ... what are they thinking??
>>>>
>>> Frankly, I don't believe it; even Microsoft can't be that stupid.
>>> And I can't find any suggestion that they've done this in a google
>>> search. I think the OP is misdiagnosing his problem.
>>>
>> An older message suggests that a service pack induced this problem, per
>> MS. I just tried it as non-admin on a W2K3 machine with recent hotfixes,
>> and the command "dir >nul" _did_ work for me.
>> Though neglected, it still sounds like a virus scanner issue to me.
>
> Yes, it seems we will need more information on this. We need someone at
> a win32 command prompt to show us a "> nul" failure.

OTOH,
what issues might arise if the output is redirected to a legal tmp file?

Regards,
Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-08-15 14:45:22 Re: [Patch] - Fix for bug #2558, InitDB failed to run
Previous Message Jim C. Nasby 2006-08-15 14:40:47 Re: An Idea for planner hints

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-08-15 14:45:22 Re: [Patch] - Fix for bug #2558, InitDB failed to run
Previous Message Simon Riggs 2006-08-15 14:31:58 Re: Forcing current WAL file to be archived