From: Steve French <smfrench@austin.rr.com>
To: eric2.valette@francetelecom.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: CIFS improvements/wider testing needed
Date: Mon, 21 Nov 2005 15:31:31 -0600 [thread overview]
Message-ID: <43823CB3.8090303@austin.rr.com> (raw)
In-Reply-To: <4382032D.4080606@francetelecom.com>
VALETTE Eric RD-MAPS-REN wrote:
>Steve French wrote:
>
>
>>Eric,
>>
>>
>Well I would be surprised the "cat >> titi" command does any of this
>byte range lock. If the "create and later rewrite the same file"
>sequence fails, with a simple cat command (cat > titi ... ^D; cat >>
>titi), how can it works with complicated applications?
>
>
>
Make sure that you let me know if your cat example works when mounted
with the relatively new "noperm" mount option on the client. At least
then we will know whether we are looking at a problem with access
control on the server (ntfs acls) or client (unix mode bits and the
.permission entry point)
next prev parent reply other threads:[~2005-11-21 21:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 16:04 CIFS improvements/wider testing needed Steve French
2005-11-21 17:26 ` VALETTE Eric RD-MAPS-REN
2005-11-21 21:28 ` Steve French
2005-11-22 9:19 ` VALETTE Eric RD-MAPS-REN
[not found] ` <43834052.4090509@austin.rr.com>
2005-11-22 16:47 ` VALETTE Eric RD-MAPS-REN
2005-11-21 21:31 ` Steve French [this message]
2005-11-22 10:36 ` VALETTE Eric RD-MAPS-REN
2005-11-22 13:57 ` VALETTE Eric RD-MAPS-REN
2005-11-22 16:30 ` CIFS emulated mode bits Steve French
2005-11-22 17:17 ` VALETTE Eric RD-MAPS-REN
[not found] ` <43834994.10006@austin.rr.com>
2005-11-22 17:24 ` CIFS improvements/wider testing needed VALETTE Eric RD-MAPS-REN
-- strict thread matches above, loose matches on Subject: below --
2005-11-22 16:40 Steve French
2005-11-21 13:02 VALETTE Eric RD-MAPS-REN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43823CB3.8090303@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=eric2.valette@francetelecom.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox