Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run
От | Andreas Pflug |
---|---|
Тема | Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run |
Дата | |
Msg-id | 44E1DDA6.5030306@pse-consulting.de обсуждение исходный текст |
Ответ на | Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run
Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run |
Список | pgsql-hackers |
Bruce Momjian wrote: > Andreas Pflug wrote: >> Tom Lane wrote: >>> Andrew Dunstan <andrew@dunslane.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
В списке pgsql-hackers по дате отправления: