| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Cc: | <pgsql-hackers-win32(at)postgresql(dot)org>, <merlin(dot)moncure(at)rcsonline(dot)com> |
| Subject: | Re: initdb crash |
| Date: | 2004-07-07 07:49:53 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE34BE04@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
> > Is anyone getting this crash when installing on ntfs an
> partition or
> > only on fat32? I have gotten the initdb crash installing on fat32.
> > Used xcacls to set permissions and got no errors!
> > However if an app is making use of these acls, I would
> assume that it
> > will crash.
> > Will try installing on ntfs partition soon.
> >
>
> Running on fat32 is just asking to be shot in the foot. If
> there is a simple check to detect it I'd favor having initdb
> and/or postgres refuse to run on fat32.
You can use GetVolumeInformation() (see MSDN). This will get you both a
set of binary flags you can check for the capabilities we want
(FS_PERSISTENT_ACLS will exist on NTFS only, for example), and a char
buffer with the name of the filesystem.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anass HAMMEDI | 2004-07-07 08:44:34 | Re: session time |
| Previous Message | Andrew Dunstan | 2004-07-06 23:01:17 | Re: initdb crash |