Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1631985 > unrolled thread

Re: [RFC] tty: pty -- Add ability to setup next pty number for ptmx open

Started byCyrill Gorcunov <gorcunov@gmail.com>
First post2017-04-27 11:30 +0200
Last post2017-04-27 11:30 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFC] tty: pty -- Add ability to setup next pty number for ptmx open Cyrill Gorcunov <gorcunov@gmail.com> - 2017-04-27 11:30 +0200

#1631985 — Re: [RFC] tty: pty -- Add ability to setup next pty number for ptmx open

FromCyrill Gorcunov <gorcunov@gmail.com>
Date2017-04-27 11:30 +0200
SubjectRe: [RFC] tty: pty -- Add ability to setup next pty number for ptmx open
Message-ID<tANUl-6Xr-7@gated-at.bofh.it>
On Fri, Mar 17, 2017 at 1:56 PM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> When we restore PTY terminals we do iterate over open() calls to reach
> the index used at checkpoint time (say application opened a number of
> terminals, then closed all other except last one) which of course very
> inconvenient.
>
> The problem get more notable in scope of controlling terminal represented
> by /dev/tty device: current CRIU restore scheme is lazy, we don't open
> files immedeately after the forks but rather defer until the whole
> process tree is created, then every process opens own files in async
> way and in result /dev/tty is not propagated into children because
> it is not yet opened.
>

Gentlemen, ping?

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web