From: Alejandro Colomar <alx.manpages@gmail.com>
To: Guillem Jover <guillem@hadrons.org>, Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/4] proc.5: Document exact /proc/PID/exe behavior on unlinked pathnames
Date: Mon, 17 Apr 2023 20:18:44 +0200 [thread overview]
Message-ID: <e242a5f9-863f-c31b-6279-cc46dffd1032@gmail.com> (raw)
In-Reply-To: <20230416233552.283776-2-guillem@hadrons.org>
[-- Attachment #1.1: Type: text/plain, Size: 1085 bytes --]
Hi Guillem,
On 4/17/23 01:35, Guillem Jover wrote:
> Add the space which gets appended before the "(deleted)" marker.
>
> Signed-off-by: Guillem Jover <guillem@hadrons.org>
Patch applied.
> ---
> man5/proc.5 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man5/proc.5 b/man5/proc.5
> index dc5397a22..1947957ad 100644
> --- a/man5/proc.5
> +++ b/man5/proc.5
> @@ -634,7 +634,7 @@ to run another copy of the same executable that is being run by
> process
> .IR pid .
> If the pathname has been unlinked, the symbolic link will contain the
> -string \[aq](deleted)\[aq] appended to the original pathname.
> +string \[aq] (deleted)\[aq] appended to the original pathname.
I used the unbreakable space instead: '\ '
Cheers,
Alex
> .\" The following was still true as at kernel 2.6.13
> In a multithreaded process, the contents of this symbolic link
> are not available if the main thread has already terminated
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-17 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 23:35 [PATCH 0/4] proc.5: Fixes and updates Guillem Jover
2023-04-16 23:35 ` [PATCH 1/4] proc.5: Document exact /proc/PID/exe behavior on unlinked pathnames Guillem Jover
2023-04-17 18:18 ` Alejandro Colomar [this message]
2023-04-16 23:35 ` [PATCH 2/4] proc.5: A process can increase its own /proc/PID/oom_adj setting Guillem Jover
2023-04-17 18:20 ` Alejandro Colomar
2023-04-16 23:35 ` [PATCH 3/4] proc.5: Document that /proc/<pid>/oom_adj is no longer present Guillem Jover
2023-04-17 18:28 ` Alejandro Colomar
2023-04-16 23:35 ` [PATCH 4/4] proc.5: tfix Guillem Jover
2023-04-17 18:29 ` 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=e242a5f9-863f-c31b-6279-cc46dffd1032@gmail.com \
--to=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=guillem@hadrons.org \
--cc=linux-man@vger.kernel.org \
/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 NNTP newsgroup(s).