hello
it works, but the logrotate is too long, and newer end in one day
so no segfault, but several logrotate process...
Still a good news.
Thanks
On Wed, 23 Jan 2019 22:42:53 +0100 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
wrote:
> Hello marc, dear Maintainer,
>
> a workaround could be to just to
hello
Thanks for all the help Bernhard, and your expertise.
Hope the maintainer will port to stretch.
It will be a great help on our production server.
Best regards
- Mail original -
De: "Bernhard Übelacker"
À: 918...@bugs.debian.org, 918106-submit...@bugs.debian.org
Envoyé: Mardi 22 Ja
hello Bernhard
there is a lot of files cause it is a syslog for thousands of servers.
between 100k and one million files a day.
coredumpctl gdb 754
PID: 754 (logrotate)
UID: 0 (root)
GID: 0 (root)
Signal: 11 (SEGV)
Timestamp: Sun 2019-01-20 11:24:28 CE
ok, so here we go
but i don't see much more withour bt full, do i understand correctly ?
the command:
coredumpctl gdb 754
display/i $pc
info reg
disassemble $pc-0x50,$pc+0x50
thanks
coredumpctl gdb 754
quit
PID: 754 (logrotate)
UID: 0 (root)
GID: 0
hi
i plan to put auditd on several hundred servers to control.
I saw this bug, but i can't confirmed it on debian jessie or stretch, and i was
thinking
it didn't exist anymore i discover the same case and behavior on ubuntu 18.40.
So now i'm in doubt :)
Jessie, 8.11 version
libpam-modules:amd6
5 matches
Mail list logo
