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 | adb8d1b17911b5c7009e292917ccc209961fdde2 (patch) | |
| tree | 4a882c572c3fc31d755098f30bb9f654f00a3251 /source3/smbd | |
| parent | 629278abdf580796ad79a7e03fedb31b49489631 (diff) | |
| download | samba-adb8d1b17911b5c7009e292917ccc209961fdde2.tar.gz samba-adb8d1b17911b5c7009e292917ccc209961fdde2.tar.bz2 samba-adb8d1b17911b5c7009e292917ccc209961fdde2.zip | |
Reformatting
(This used to be commit fb900184feeda37691cf9bd57c029988648de9f8)
Diffstat (limited to 'source3/smbd')
| -rw-r--r-- | source3/smbd/nttrans.c | 22 |
1 files changed, 12 insertions, 10 deletions
diff --git a/source3/smbd/nttrans.c b/source3/smbd/nttrans.c index 9e6b933b64..aed237fc65 100644 --- a/source3/smbd/nttrans.c +++ b/source3/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. */ |