<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2016年02月15日 20:31, Burton, Ross
wrote:<br>
</div>
<blockquote
cite="mid:CAJTo0LaQ-viF19UDx0XAVFiEi=7a+rf6maPfjr-6QSLhVwRSSQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 15 February 2016 at 01:59, <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:kai.kang@windriver.com" target="_blank">kai.kang@windriver.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":2u7" class="a3s" style="overflow:hidden">+
eval flock -x -w 100
$rootdir/tmp/user-and-group-ops.flock -c \'$PSEUDO
useradd $opts\' || true<br>
</div>
</blockquote>
</div>
<br>
This is a great patch, but why not just flock $rootdir/etc
instead of new file in tmp? Surely images end up being
created with /tmp/user-and-group-ops.flock in them?</div>
</div>
</blockquote>
<br>
I didn't try to think take a directory as a lock and I'll try it.
For the lock file in $rootdir/tmp/, it is ok that /tmp will be
remounted and user won't see the lock file.<br>
<br>
Thanks,<br>
Kai<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAJTo0LaQ-viF19UDx0XAVFiEi=7a+rf6maPfjr-6QSLhVwRSSQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Ross</div>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Regards,
Neil | Kai Kang</pre>
</body>
</html>