diff options
| author | Volker Lendecke <vl@sernet.de> | 2007-12-01 14:57:46 +0100 |
|---|---|---|
| committer | Volker Lendecke <vl@sernet.de> | 2007-12-05 13:45:11 +0100 |
| commit | fb900184feeda37691cf9bd57c029988648de9f8 (patch) | |
| tree | 37ac94a6bdd5e8574dfef789f487f9e86e4d6360 /source/smbd/nttrans.c | |
| parent | f6d62226a33cdff41ad7881996d856b7130ef15c (diff) | |
| download | samba-fb900184feeda37691cf9bd57c029988648de9f8.tar.gz samba-fb900184feeda37691cf9bd57c029988648de9f8.tar.xz samba-fb900184feeda37691cf9bd57c029988648de9f8.zip | |
Reformatting
Diffstat (limited to 'source/smbd/nttrans.c')
| -rw-r--r-- | source/smbd/nttrans.c | 22 |
1 files changed, 12 insertions, 10 deletions
diff --git a/source/smbd/nttrans.c b/source/smbd/nttrans.c index 9e6b933b645..aed237fc65b 100644 --- a/source/smbd/nttrans.c +++ b/source/smbd/nttrans.c @@ -759,11 +759,12 @@ void reply_ntcreate_and_X(connection_struct *conn, return; } - /* This is the correct thing to do (check every time) but can_delete is - expensive (it may have to read the parent directory permissions). So - for now we're not doing it unless we have a strong hint the client - is really going to delete this file. If the client is forcing FILE_CREATE - let the filesystem take care of the permissions. */ + /* This is the correct thing to do (check every time) but can_delete + * is expensive (it may have to read the parent directory + * permissions). So for now we're not doing it unless we have a strong + * hint the client is really going to delete this file. If the client + * is forcing FILE_CREATE let the filesystem take care of the + * permissions. */ /* Setting FILE_SHARE_DELETE is the hint. */ @@ -1505,11 +1506,12 @@ static void call_nt_transact_create(connection_struct *conn, return; } - /* This is the correct thing to do (check every time) but can_delete is - expensive (it may have to read the parent directory permissions). So - for now we're not doing it unless we have a strong hint the client - is really going to delete this file. If the client is forcing FILE_CREATE - let the filesystem take care of the permissions. */ + /* This is the correct thing to do (check every time) but can_delete + * is expensive (it may have to read the parent directory + * permissions). So for now we're not doing it unless we have a strong + * hint the client is really going to delete this file. If the client + * is forcing FILE_CREATE let the filesystem take care of the + * permissions. */ /* Setting FILE_SHARE_DELETE is the hint. */ |