public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page credentials.7
Date: Sun, 4 Dec 2022 21:59:35 +0100	[thread overview]
Message-ID: <e77108eb-13ca-eb3a-fe42-88efa6add511@gmail.com> (raw)
In-Reply-To: <20221204090727.GA1416@Debian-50-lenny-64-minimal>


[-- Attachment #1.1: Type: text/plain, Size: 1032 bytes --]

Hi Helge,

On 12/4/22 10:07, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    from background job → from a background job

I did "background jobs".  Fixed.  Thanks!

Cheers,

Alex

> 
> "At most one of the jobs in a session may be the I<foreground job>; other"
> "jobs in the session are I<background jobs>.  Only the foreground job may"
> "read from the terminal; when a process in the background attempts to read"
> "from the terminal, its process group is sent a B<SIGTTIN> signal, which"
> "suspends the job.  If the B<TOSTOP> flag has been set for the terminal (see"
> "B<termios>(3)), then only the foreground job may write to the terminal;"
> "writes from background job cause a B<SIGTTOU> signal to be generated, which"
> "suspends the job.  When terminal keys that generate a signal (such as the"
> "I<interrupt> key, normally control-C)  are pressed, the signal is sent to"
> "the processes in the foreground job."

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-04 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04  9:07 Issue in man page credentials.7 Helge Kreutzmann
2022-12-04 20:59 ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-04  9:07 Helge Kreutzmann
2022-12-04 21:00 ` Alejandro Colomar

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

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

  git send-email \
    --in-reply-to=e77108eb-13ca-eb3a-fe42-88efa6add511@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.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