unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: vapnik spaknik via General Guile related discussions <guile-user@gnu.org>
To: Sebastian Miele <sebastian.miele@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: how to kill child process?
Date: Mon, 24 Aug 2020 16:51:01 +0000 (UTC)	[thread overview]
Message-ID: <663933226.5501400.1598287861052@mail.yahoo.com> (raw)
In-Reply-To: <87a6ykm845.fsf@gmail.com>

 

>On Monday, August 24, 2020, 03:27:57 PM GMT+1, Sebastian Miele <sebastian.miele@gmail.com> wrote:
>
>Look at output of the following:
>
>  pkill ssh
>  ssh -S '~/.ssh/socket/%C' -N -M -f <host> &
>  echo $!
>  pgrep -a ssh
>
>Then look at the output of:
>
> pkill ssh
>  ssh -S '~/.ssh/socket/%C' -N -M <host> &
>  echo $!
>  pgrep -a ssh
>
>Passing '-f' does make 'ssh' fork.
>
>Not using '-f' does not make 'ssh' fork.  (At least the current 'ssh' on
>my machine.  I do not know whether OpenSSH in any way guarantees that
>behavior in the future.)

Even without the '-f' flag I still get the same problem in guile.
If I print the pid of the child process I can see that it is different from the pid of the ssh process.  


  parent reply	other threads:[~2020-08-24 16:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2139767403.5164633.1598212258730.ref@mail.yahoo.com>
2020-08-23 19:50 ` how to kill child process? vapnik spaknik
2020-08-23 20:31   ` Sebastian Miele
2020-08-23 23:08     ` Sebastian Miele
2020-08-24 11:07     ` vapnik spaknik via General Guile related discussions
2020-08-24 12:05   ` Sebastian Miele
2020-08-24 13:15     ` vapnik spaknik via General Guile related discussions
2020-08-24 14:27       ` Sebastian Miele
2020-08-24 14:33         ` Sebastian Miele
2020-08-24 16:51         ` vapnik spaknik via General Guile related discussions [this message]
2020-08-24 18:47           ` Sebastian Miele
2020-08-25 18:21             ` vapnik spaknik via General Guile related discussions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=663933226.5501400.1598287861052@mail.yahoo.com \
    --to=guile-user@gnu.org \
    --cc=sebastian.miele@gmail.com \
    --cc=vapniks@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).