On Thu, Jun 13, 2013 at 9:14 AM, Ben Pfaff <span dir="ltr"><<a href="mailto:blp@nicira.com" target="_blank">blp@nicira.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, Jun 13, 2013 at 08:29:25AM -0700, Gurucharan Shetty wrote:<br>
> On Wed, Jun 12, 2013 at 5:10 PM, Ben Pfaff <<a href="mailto:blp@nicira.com">blp@nicira.com</a>> wrote:<br>
</div><div class="im">> > This is unpolished but it shows the approach I have in mind.<br>
> > Sending out for comments on the approach.<br>
> ><br>
> I am fine with the approach. The two negatives I see with this:<br>
> * If /tmp is cleaned up routinely, we will loose the information. If we<br>
> decide to put this in /etc/openvswitch, it may look a little dirty when<br>
> program is abnormally terminated.<br>
<br>
</div>tmpfile() normally creates a file and then deletes it anyhow. I don't<br>
know of any /tmp reaper that can affect it.<br>
<div class="im"><br>
> * If we have multiple run time data, (ex: add/remove databases) we may need<br>
> multiple files.<br>
<br>
</div>I thought that we could simply use a little more sophisticated JSON.<br>
Is there a reason why not?<br></blockquote><div>No reason. I did not realize that you intended to do this with a single file. </div></div><br><div>I guess, then this fine.</div>