Re: Frequent network code panics

To: Masanobu SAITOH <msaitoh%execsw.org@localhost>
Subject: Re: Frequent network code panics
From: Hauke Fath <hf%spg.tu-darmstadt.de@localhost>
Date: Wed, 29 Mar 2017 08:52:14 +0200

On Wed, 29 Mar 2017 13:54:29 +0900, Masanobu SAITOH wrote:
> someone (carp, pf or othes) broke memory?

"broke" meaning what, exactly? Locking issues, stack corruption?

I seem to sense a pattern related to (internal) traffic - the primary 
is more likely to crash during nightly backup runs, or on busy days 
like Mondays.

Cheerio,
Hauke

-- 
     The ASCII Ribbon Campaign                    Hauke Fath
()     No HTML/RTF in email            Institut für Nachrichtentechnik
/\     No Word docs in email                     TU Darmstadt
     Respect for open standards              Ruf +49-6151-16-21344

Follow-Ups:
- Re: Frequent network code panics
  - From: Masanobu SAITOH

References:
- Frequent network code panics
  - From: Hauke Fath
- Re: Frequent network code panics
  - From: Masanobu SAITOH
- Re: Frequent network code panics
  - From: Hauke Fath
- Re: Frequent network code panics
  - From: Masanobu SAITOH

Prev by Date: Re: Frequent network code panics
Next by Date: Re: Frequent network code panics
Previous by Thread: Re: Frequent network code panics
Next by Thread: Re: Frequent network code panics
Indexes:

Home | Main Index | Thread Index | Old Index