Re: Initdb on Windows 2003
От | |
---|---|
Тема | Re: Initdb on Windows 2003 |
Дата | |
Msg-id | 2E22904642859A40AF5E1CA1597EBB1F02EF42EF@devexmb1.corp.nai.org обсуждение исходный текст |
Ответ на | Initdb on Windows 2003 (<James_Hughes@McAfee.com>) |
Список | pgsql-hackers |
Just to let you guys know, I spoke to Microsoft and they confirmed that they have restricted access to the 'nul' device in a security update (to admin users). Not quite sure of the extact update! This is hardcoded in the Windows source, so no way to change somthing via code :( - James -----Original Message----- From: Magnus Hagander [mailto:mha@sollentuna.net] Sent: 03 March 2006 15:18 To: Hughes, James; andrew@dunslane.net Cc: pgsql-hackers@postgresql.org Subject: RE: [HACKERS] Initdb on Windows 2003 > I did run filemon but did not get anything from it :( Yes I disabled > all anti-virus software, no difference made. Even more interesting. Do you have any other filter drivers that you know of? SOme kind of quota stuff or so perhaps? Oh, and if the bug is in the AV filter driver it's often not enough to disable the AV - it has to be completely uninstalled. I've seen this with several products wrt LSPs, and at least once with filterdrivers. So that's also worth a try. > Have raised a helpdesk ticket with Microsoft, see if they can shed any > light on the problem. Sounds good - since you can reproduce it with a simple commandline, they should at least accept touching the case ;-) //Magnus
В списке pgsql-hackers по дате отправления: