From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: [PATCH] vnstat: Update to 1.18
Date: Wed, 21 Mar 2018 20:30:04 +0100
Message-ID:
 <trinity-57660a8c-7e59-4ed6-b024-7c803e7bb812-1521660604280@3c-app-gmx-bs30>
In-Reply-To: <275d22f3-bc8f-e125-79ee-0b73f356c4f9@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2169496965544744238=="
List-Id: <development.lists.ipfire.org>

--===============2169496965544744238==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


> Gesendet: Mittwoch, 21. M=C3=A4rz 2018 um 18:38 Uhr
> Von: "Matthias Fischer" <matthias.fischer(a)ipfire.org>
> An: "Michael Tremer" <michael.tremer(a)ipfire.org>, "IPFire: Development-Li=
st" <development(a)lists.ipfire.org>
> Betreff: Re: [PATCH] vnstat: Update to 1.18
>
> >=20
> > P.S. I did not appreciate that comment of that forum user about this bug.=
 Bugs
> > happen. If he doesn't like it, he can take lots of =E2=82=AC=E2=82=AC=E2=
=82=AC=E2=82=AC into his hand and pay
> > other people to get their bugs.
>=20
> Me too. But I tried to be patient, took a deep breath and tried to keep
> calm and ~professional. Wasn't easy. Besides, I don't think this is
> really a "bug". 'vnstat' can handle his speed and download rates with no
> problems. It just happened that they were a bit too much for the
> standard config - in *his* case.
>=20
> Best,
> Matthias
>=20
>=20
Hi,

just my opinion ( I've investigated now a bit about this "problem" ;) )
The "solution" isn't really that. The changed parameter is only used by vnsta=
td, which isn't used in IPFire. I can't imagine what did the remedy.
We don't know exactly his configuration. Therefore I gave him some hints to h=
elp clarifying the case.
If he doesn't answer, just forget his unqualified comment.

Best,
Bernhard

--===============2169496965544744238==--