On Thu, Oct 31, 2019 at 06:30:33PM +0100, Lennart Poettering wrote:
> On Mo, 21.10.19 17:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > In principle, the watchdog for services is nice. But in practice it seems
> > be bring only grief. The Fedora bugtracker is full of automated
On Mo, 21.10.19 17:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> In principle, the watchdog for services is nice. But in practice it seems
> be bring only grief. The Fedora bugtracker is full of automated reports of
> ABRTs,
> and of those that were fired by the watchdog, pretty
On Fri, Oct 25, 2019 at 10:26:44AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Oct 24, 2019 at 02:56:55PM -0700, Vito Caputo wrote:
> > On Thu, Oct 24, 2019 at 10:45:32AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Tue, Oct 22, 2019 at 04:35:13AM -0700, Vito Caputo wrote:
> > > > On
On Thu, Oct 24, 2019 at 02:56:55PM -0700, Vito Caputo wrote:
> On Thu, Oct 24, 2019 at 10:45:32AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Oct 22, 2019 at 04:35:13AM -0700, Vito Caputo wrote:
> > > On Tue, Oct 22, 2019 at 10:51:49AM +, Zbigniew Jędrzejewski-Szmek
> > > wrote:
> >
On Thu, Oct 24, 2019 at 10:45:32AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Oct 22, 2019 at 04:35:13AM -0700, Vito Caputo wrote:
> > On Tue, Oct 22, 2019 at 10:51:49AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Tue, Oct 22, 2019 at 12:34:45PM +0200, Umut Tezduyar Lindskog wrote:
On Tue, Oct 22, 2019 at 04:35:13AM -0700, Vito Caputo wrote:
> On Tue, Oct 22, 2019 at 10:51:49AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Oct 22, 2019 at 12:34:45PM +0200, Umut Tezduyar Lindskog wrote:
> > > I am curious Zbigniew of how you find out if the coredump was on a starved
>
On Tue, Oct 22, 2019 at 10:51:49AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Oct 22, 2019 at 12:34:45PM +0200, Umut Tezduyar Lindskog wrote:
> > I am curious Zbigniew of how you find out if the coredump was on a starved
> > process?
>
> A very common case is systemd-journald which gets
On Tue, Oct 22, 2019 at 12:34:45PM +0200, Umut Tezduyar Lindskog wrote:
> I am curious Zbigniew of how you find out if the coredump was on a starved
> process?
A very common case is systemd-journald which gets SIGABRT when in a
read() or write() or similar syscall. Another case is when
I am curious Zbigniew of how you find out if the coredump was on a starved
process?
This is common for our embedded devices. I didn't think it is common for
desktop too.
It is really useful for getting coredumps on deadlocked applications. For
that reason I don't think it is good to remove this
On Tue, 22 Oct 2019 09:17:42 +
Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Oct 22, 2019 at 09:54:31AM +0300, Pekka Paalanen wrote:
> > On Mon, 21 Oct 2019 17:50:44 +
> > Zbigniew Jędrzejewski-Szmek wrote:
> >
> > > In principle, the watchdog for services is nice. But in practice it
On Mon, Oct 21, 2019 at 02:32:08PM -0700, Vito Caputo wrote:
> On Mon, Oct 21, 2019 at 05:50:44PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > In principle, the watchdog for services is nice. But in practice it seems
> > be bring only grief. The Fedora bugtracker is full of automated reports of
On Tue, Oct 22, 2019 at 09:54:31AM +0300, Pekka Paalanen wrote:
> On Mon, 21 Oct 2019 17:50:44 +
> Zbigniew Jędrzejewski-Szmek wrote:
>
> > In principle, the watchdog for services is nice. But in practice it seems
> > be bring only grief. The Fedora bugtracker is full of automated reports of
On Mon, 21 Oct 2019 17:50:44 +
Zbigniew Jędrzejewski-Szmek wrote:
> In principle, the watchdog for services is nice. But in practice it seems
> be bring only grief. The Fedora bugtracker is full of automated reports of
> ABRTs,
> and of those that were fired by the watchdog, pretty much
On Mon, Oct 21, 2019 at 05:50:44PM +, Zbigniew Jędrzejewski-Szmek wrote:
> In principle, the watchdog for services is nice. But in practice it seems
> be bring only grief. The Fedora bugtracker is full of automated reports of
> ABRTs,
> and of those that were fired by the watchdog, pretty
14 matches
Mail list logo