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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
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 13:54:50
Message-ID: 200608151354.k7FDspr23535@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2006-08-15 13:59:09 Re: [PATCHES] Custom variable class segmentation fault
Previous Message dror 2006-08-15 13:32:49 Re: [HACKERS] [Patch] - Fix for bug #2558, InitDB failed

Browse pgsql-patches by date

  From Date Subject
Next Message Zdenek Kotala 2006-08-15 13:59:09 Re: [PATCHES] Custom variable class segmentation fault
Previous Message dror 2006-08-15 13:32:49 Re: [HACKERS] [Patch] - Fix for bug #2558, InitDB failed