On Tue, Apr 29, 2014 at 11:23 PM, Simo Sorce <simo@redhat.com> wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">
can you use an actual chroot ?</div></blockquote><div><br></div><div>Calling chroot tends to imply running code from the target system. I'd prefer to avoid that by default. In practice some things are going to require it, but the more we can avoid it, the better.</div><div><br></div><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">I am not sure I understand the fdatasync() argument here ?
sssd uses a database, so it is indeed probably "heavy" on f(data)sync
for your standards (?).</div></blockquote><br><div>It's not about how heavy the use of fsync is - it's whether to do it at all. There are two cases where we *don't* want to fsync - mock chroots and initial installs in Anaconda. For the other cases, like upgrading a running system, we do.</div><div><br></div><div><br></div>