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 [thread overview]
Message-ID: <trinity-57660a8c-7e59-4ed6-b024-7c803e7bb812-1521660604280@3c-app-gmx-bs30> (raw)
In-Reply-To: <275d22f3-bc8f-e125-79ee-0b73f356c4f9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
> Gesendet: Mittwoch, 21. März 2018 um 18:38 Uhr
> Von: "Matthias Fischer" <matthias.fischer(a)ipfire.org>
> An: "Michael Tremer" <michael.tremer(a)ipfire.org>, "IPFire: Development-List" <development(a)lists.ipfire.org>
> Betreff: Re: [PATCH] vnstat: Update to 1.18
>
> >
> > 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 €€€€ into his hand and pay
> > other people to get their bugs.
>
> 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.
>
> Best,
> Matthias
>
>
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 vnstatd, 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 help clarifying the case.
If he doesn't answer, just forget his unqualified comment.
Best,
Bernhard
next prev parent reply other threads:[~2018-03-21 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 19:46 Matthias Fischer
2018-03-20 20:34 ` Michael Tremer
2018-03-21 17:38 ` Matthias Fischer
2018-03-21 19:30 ` Bernhard Bitsch [this message]
2018-03-23 12:39 ` Aw: " Bernhard Bitsch
2018-03-23 14:54 ` Michael Tremer
2018-03-28 11:55 ` Aw: " Bernhard Bitsch
2018-03-28 18:04 ` Michael Tremer
2018-03-28 21:47 ` Aw: " Bernhard Bitsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-57660a8c-7e59-4ed6-b024-7c803e7bb812-1521660604280@3c-app-gmx-bs30 \
--to=bernhard.bitsch@gmx.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox