<br><br><div class="gmail_quote">2010/10/10 Wayne Davison <span dir="ltr"><<a href="mailto:wayned@samba.org">wayned@samba.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Thu, Oct 7, 2010 at 7:57 AM, thomas veymont <span dir="ltr"><<a href="mailto:thomas.veymont@gmail.com" target="_blank">thomas.veymont@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As far as I know, I should setup 2 distinct modules with different permissions, but sharing the same physical directory.<br></blockquote><div><br></div></div><div>Right. That's the only solution for now. The patch you cited (which should eventually be promoted to the 3.1.0dev code) does allow differentiation of ro/rw based on user, but some kind of user/group login is required (e.g. password-less anonymous access won't ever succeed for a module that has auth defined).</div>
<div><br></div><div>One thing that can help out with the configuration of multiple modules is available if you're using the 3.1.0dev (git) release, you can use a "&merge file" directive to read the common settings from one place:</div>
<div><br></div><div>[foobar]</div><div> &merge /some/foobar.conf</div><div> read only = yes</div><div>[foobar-auth]</div><div> &merge /some/foobar.conf</div>
<div><div> read only = no</div><div> auth users = joe sam jane</div></div><div><br></div><div>You'd put the "path = /whatever" (etc.) settings in the foobar.conf file.</div>
<div><br></div><font color="#888888"><div>..wayne..</div></font></div>
</blockquote></div><br>thanks for these advices, that was helpful<br><br>Tom