summaryrefslogtreecommitdiff
path: root/docs/docbook/dbsgml
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2001-04-14 20:47:30 +0000
committerJeremy Allison <jra@samba.org>2001-04-14 20:47:30 +0000
commit2df39394fe01de6fb19cd919554272f407ecee4a (patch)
treeff3741febe9a5b334a78d2953a97685fe9cfb2f9 /docs/docbook/dbsgml
parented449b8ca7697d64ab3cfe8289287dd18566c91e (diff)
downloadsamba-2df39394fe01de6fb19cd919554272f407ecee4a.tar.gz
samba-2df39394fe01de6fb19cd919554272f407ecee4a.tar.bz2
samba-2df39394fe01de6fb19cd919554272f407ecee4a.zip
This little piece of insanity is inspired by the
fact that an NT client can open a file for O_RDONLY, but set the create disposition to FILE_EXISTS_TRUNCATE. If the client *can* write to the file, then it expects to truncate the file, even though it is opening for readonly. Quicken uses this stupid trick in backup file creation... Thanks *greatly* to "David W. Chapman Jr." <dwcjr@inethouston.net> for helping track this one down. It didn't bite us in 2.0.x as we always opened files read-write in that release. Jeremy. (This used to be commit 5baef56831f9bc4fa10a851abd5f9305b974fb3b)
Diffstat (limited to 'docs/docbook/dbsgml')
0 files changed, 0 insertions, 0 deletions