From: Jonny Grant <jg@jguk.org>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: Re: core(5)
Date: Sat, 6 Jun 2020 16:45:11 +0100 [thread overview]
Message-ID: <e8283646-38fd-b9a8-2056-547fecaeb182@jguk.org> (raw)
In-Reply-To: <20200606145003.x37j5hywuyn32lpf@jwilk.net>
On 06/06/2020 15:50, Jakub Wilk wrote:
> * Jonny Grant <jg@jguk.org>, 2020-06-06, 14:18:
>> 3) Could i ask to clarify my understanding. For this "The binary being executed by the process does not have read
>> permission enabled."
>> -- is this when the binary permissions are changed after it starts running?
>
> No, AFAICS the permission check is done when the process starts.
How can the process start if the binary file doesn't have read permissions enabled?
>> 4) I noticed %P always gave me P1200 even after a reboot I recall, I had expected it be '1', do you see similar?
>
> Here %P expands to the pid of the process, as expected:
>
> $ uname -rv
> 5.6.0-2-amd64 #1 SMP Debian 5.6.14-1 (2020-05-23)
>
> $ sudo sysctl -w kernel.core_pattern="%P-%e-%s.core"
> kernel.core_pattern = %P-%e-%s.core
>
> $ ulimit -c unlimited
>
> $ sh -c 'kill -ABRT $$'
> Aborted (core dumped)
>
> $ ls *.core
> 7154-sh-6.core
My apologies, it was P1000. This was from two different runs, 2 days apart.
I think this was "P%P-T%i%e-%s-T%t". I tried to reproduce today, but couldn't
-rw------- 1 jonny jonny 99041280 May 27 21:42 P1000-T18441Process-5-T1590612166.core
-rw------- 1 jonny jonny 104407040 May 29 23:24 P1000-T5804Process-5-T1590791098.core
Cheers, Jonny
next prev parent reply other threads:[~2020-06-06 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 13:18 core(5) Jonny Grant
2020-06-06 14:50 ` core(5) Jakub Wilk
2020-06-06 15:45 ` Jonny Grant [this message]
2020-06-06 18:32 ` core(5) Jakub Wilk
2020-06-06 19:39 ` core(5) Michael Kerrisk (man-pages)
2020-06-06 21:16 ` core(5) Jonny Grant
2020-06-08 16:18 ` core(5) Michael Kerrisk (man-pages)
2020-06-08 16:06 ` core(5) Michael Kerrisk (man-pages)
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=e8283646-38fd-b9a8-2056-547fecaeb182@jguk.org \
--to=jg@jguk.org \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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;
as well as URLs for NNTP newsgroup(s).