Re: IPTables stops logging after long uptime

From: Richard Dicaire (rdicaire@kritek.net)
Date: 02/09/03

  • Next message: Andrew Griffiths: "Re: IPTables stops logging after long uptime" 
    Date: Sat, 08 Feb 2003 19:41:41 -0500
From: Richard Dicaire <rdicaire@kritek.net>
To: Chris Travers <chris@travelamericas.com>

    Chris Travers wrote:
    > kernel. Note that restarting Syslog does not solve the problem, and
    > syslog does log everything else correctly. so the problem appears to be
    > with the kernel at this point.

    Restart klogd, its not syslogd.

    Relevant Pages

    • Re: [PATCH 00/23] per device dirty throttling -v8
      ... an XT when copying large files" bugzilla entry: ... start a large kernel build with DEBUG_INFO on a quad-core 4GB RAM box, ... I've got a syslog server that's got two Opteron 246 cpu's, 16G ram, 2x140G ...
      (Linux-Kernel)
    • Re: [PATCH 00/23] per device dirty throttling -v8
      ... start a large kernel build with DEBUG_INFO on a quad-core 4GB RAM box, ... I've got a syslog server that's got two Opteron 246 cpu's, 16G ram, 2x140G ... cron job copies the data to the raid array. ...
      (Linux-Kernel)
    • Re: Linux Boot-up Screens
      ... before the kernel is loaded and started. ... > The command "dmesg" dumps the contents of the kernel ring buffer. ... However, syslog is very customizable, you can have ... > programs, as long as we are talking about sysvinit scripts, are logged ...
      (comp.os.linux.misc)
    • Re: [PATCH 00/23] per device dirty throttling -v8
      ... start a large kernel build with DEBUG_INFO on a quad-core 4GB RAM box, ... I've got a syslog server that's got two Opteron 246 cpu's, 16G ram, 2x140G ... I have syslog doing buffered writes to the SCSI drives and every 5 min a cron job copies the data to the raid array. ... I've experimented with nice levels (nicing down the grep and nicing up the syslogd) without a noticable effect on the losses. ...
      (Linux-Kernel)
    • [2.6.18-rc7] printk output delay in syslog wrt dmesg still unfixed
      ... which I reported for kernel 2.6.18-rc1 on my ... output from printkappears in syslog (eg. ...
      (Linux-Kernel)