On Tue, 2019-03-19 at 16:26 +0100, Jakub Wilk wrote:
> * Paul Wise , 2019-03-19, 12:12:
>
> > Now I wonder how to add %c to the core_pattern and also deal with old
> > versions of Linux.
>
> %c and argument splitting were added in the same commit:
> https://github.com/torvalds/linux/commit/74aad
* Paul Wise , 2019-03-19, 12:12:
You can use %c in core_pattern to get the soft limit of the crashing
process.
(Hmm, it's not documented what's the value you get when there's no
limit...)
I got 0x on amd64 when it was set to unlimited,
That's a bit ugly, but convenient, bec
On Sat, 2019-03-16 at 12:10 +0100, Jakub Wilk wrote:
> You can use %c in core_pattern to get the soft limit of the crashing
> process.
>
> (Hmm, it's not documented what's the value you get when there's no
> limit...)
I got 0x on amd64 when it was set to unlimited, which
corres
* Paul Wise , 2019-03-16, 18:43:
* corekeeper doesn't enforce this limit on its own either.
Should corekeeper use `ulimit -c` to retrieve the limit?
That would give you the limit for the core handler process, not for the
process that crashed.
You can use %c in core_pattern to get the soft l
Control: tags -1 + security
On Sat, 2019-03-16 at 11:08 +0100, Jakub Wilk wrote:
> The package description says that you can disable core dumping in
> /etc/security/limits.d/corekeeper.conf, but this doesn't work on Linux,
This feels like a DoS attack since the disk could fill up.
> * The ker
Package: corekeeper
Version: 1.6
The package description says that you can disable core dumping in
/etc/security/limits.d/corekeeper.conf, but this doesn't work on Linux,
because:
* The kernel (intentionally) doesn't enforce the RLIMIT_CORE when a core
dump handler is installed.
* corekeep
6 matches
Mail list logo
