All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Leach <raymondl@knowledgefactory.co.za>
To: steve.cherry@brandid.net
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>,
	GLUG Tech <glug-tech@linux.org.za>
Subject: Re: ntop not saving ...
Date: 19 Jun 2003 13:13:25 +0200	[thread overview]
Message-ID: <1056021204.1490.41.camel@raylinux.internal> (raw)
In-Reply-To: <3EF19644.9050401@brandid.net>

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

On Thu, 2003-06-19 at 12:53, Steven Cherry wrote:
> hello,
> 
> I had this problem with servers who's network load was quite high and 
> when you restart it all your logs are gone and you have to start a fresh?
> 
That is exactly what is happening.

I'm going to try the new 2.2 version and see what happens.

> Never got to the bottom of it though, I would be intrested to hear if 
> you do though
> 
> thanks
> 
> 
> steve
> 
> Ray Leach wrote:
> > Hi
> > 
> > Has anyone used ntop to monitor network load?
> > 
> > My ntopd keeps dying with no evidence as to why. No messages on console
> > or in /var/log/messages.
> > 
> > Any clues as to what is happening?
> > 
> > 
> 
> 
> ----------------------------------------------
> This message has been scanned for viruses and
> dangerous content by the Brand I.D. Ltd E-mail
> Virus Scanner, and is believed to be clean.
> 
> http://www.brandid.net
-- 
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD  00EE 8757 EE47 F06F FB28
--

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-06-19 11:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 10:40 ntop not saving Ray Leach
     [not found] ` <3EF19644.9050401@brandid.net>
2003-06-19 11:13   ` Ray Leach [this message]

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=1056021204.1490.41.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.co.za \
    --cc=glug-tech@linux.org.za \
    --cc=netfilter@lists.netfilter.org \
    --cc=steve.cherry@brandid.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.