[CRIU] Losing logs after second restore?

[Francisco Tolmasky]

So apparently node hates this (and it is expected behavior for it to
through an error when its truncated: https://www.npmjs.com/package/epipebomb
). I am very unfamiliar with this, can yu explain why criu opens files with
O_TRUNC flags (and what would happen if we changed that?).

Thanks,

Francisco

On Fri, Aug 21, 2015 at 11:18 AM, Pavel Emelyanov <xemul at parallels.com>
wrote:

> On 08/21/2015 09:16 PM, Francisco Tolmasky wrote:
> > Sorry, just so I understand correctly, does this result in expected
> behavior that *new*
> > logs won't show up
>
> Well, no, new logs will (should) show up in the file. Provided criu starts
> at all :)
>
> > (I see the logs from the initial run and restore, but no more after that)
> >
> > On Friday, August 21, 2015, Pavel Emelyanov <xemul at parallels.com
> <mailto:xemul at parallels.com>> wrote:
> >
> >     On 08/20/2015 08:09 AM, Francisco Tolmasky wrote:
> >     > Does anything come to mind as to why we wouldn’t see logs after
> two restores?
> >
> >     CRIU opens log files with O_TRUNC flags, thus killing the previous
> contents of it.
> >
> >
> >
> > --
> > Francisco Tolmasky
> > www.tolmasky.com <http://www.tolmasky.com>
> > tolmasky at gmail.com <mailto:tolmasky at gmail.com>
>
>


-- 
Francisco Tolmasky
www.tolmasky.com
tolmasky at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20150901/b53ba751/attachment.html>