<div><br></div>Tahnks guys!<br><br><div class="gmail_quote">2013/1/30 Karaoui mohamed lamine <span dir="ltr"><<a href="mailto:moharaka@gmail.com" target="_blank">moharaka@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
thanks, i think i get it.<br><br><div class="gmail_quote">2013/1/30 <span dir="ltr"><<a href="mailto:Valdis.Kletnieks@vt.edu" target="_blank">Valdis.Kletnieks@vt.edu</a>></span><div><div class="h5"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Tue, 29 Jan 2013 20:16:26 +0100, you said:<br>
<br>
> Actually my question is :<br>
> Does POSIX specifies the fact that we need to use "lockf" to be able to do<br>
> read/write operation in different offset ? Is'n the kernel supposed to<br>
> ensure this ?<br>
<br>
</div>If you have non-overlapping writes, the kernel will eventually sort it out<br>
for you. If your writes overlap, you'll have to provide your own locking<br>
via lockf() or similar, and synchronization via other methods.<br>
</blockquote></div></div></div><br>
</blockquote></div><br>