Hi,
I run debian unstable and klogd seemed to eat all the CPU. I guessed it
was an error in that package so I removed it and installed metalog. But
now metalog is eating 100% CPU.
There is no excessive logging going on as i can see in syslog so I see
no reason why it should eat so much CPU
Adam Byrtek wrote:
- unmaintained
I'll try to maintain it better then the previous maintainer...
I'm a user of debian unstable on the desktop.
I'm glad to see this, I was slightly confused that one day i saw this
package removed, checked bug reports and didn't find anything reasonable
about the 'w
ps booting in
> qwerty.
>
> Benedict
Apparently, there is an error in the testing/unstable console-common
packages. I tried installing console-common from stable, testing and
unstable and ony the stable package worked!
Other people (i think i saw it also in the german and french user lists)
Op di 09-09-2003, om 22:21 schreef Benedict Verheyen:
> Hi,
>
> after dpkg became unworkable, i reinstalled my server.
> I encountered a couple of very annoying problems after upgrading to
> testing and that's with an almost bare system!
> (console problem and logger problem where there before upg
t to the
console. I know i can turn this off by typing dmesg -n 3 and i can do it
automatically at boottime by adjusting /etc/init.d/klogd and setting
options like KLOGD="-c 3". How come after booting (and not yet being
logged in) messages are sent to tty1? Imagine trying to type your login
Good day!
I've got some problems with klogd on 2 different servers.
First one is debian woody+2.2.20 and second is debian
woody+2.4.20, both has kernels compiled by hand,
sysklogd 1.4.1-10 and klogd 1.4.1-10.
When system is operating i don't see any firewall messages
in /var/log/syslog.
On Wed, 2001-11-28 at 12:51, Gabor Gludovatz wrote:
> Hi,
>
> could someone please tell me how could I get klogd not to log every event
> to the console as well? syslog logging would be enough, but I haven't
> found any switch or configuration parameter...
> syslog.conf is
Hi,
could someone please tell me how could I get klogd not to log every event
to the console as well? syslog logging would be enough, but I haven't
found any switch or configuration parameter...
syslog.conf is set up correctly and if I kill klogd, there are no kernel
messages on the console.
Quoting Christopher S. Swingley <[EMAIL PROTECTED]>:
> OK, I'm going crazy here trying to get iptables to log packets to a
> file called /var/log/kern.info.
> What am I missing? And what is the right procedure to clear a log
> without causing sysklogd / klogd to choke
-/var/log/kern.info
But /var/log/kern.info is empty:
-rw-r-1 root adm0 Jul 30 10:04 /var/log/kern.info
I've stopped and started /etc/init.d/sysklogd and /etc/init.d/klogd
multiple times (and in various orders), as well as re-running iptables.
I've also tri
On Sat, Apr 14, 2001 at 01:06:41PM -0700, Peter Jay Salzman wrote:
> dear all,
>
> i just updated woody and klogd has disappeared into thin air.
It's found in the klogd package.
--
Nathan Norman - Staff Engineer | A good plan today is better
Micromuse Ltd. | than
On Saturday 14 April 2001 14:51, you wrote:
> Hello,
>
> Not sure if I can help clear this up, as I run sid(unstable). But i get the
> following info from dpkg -p sysklogd
>
> Provides: syslogd, system-log-daemo
> Recommends: klogd | linux-kernel-log-daemon
>
>
>
I don't know what is going on here, but klogd isn't the only package that has
disappeared from woody. Sawfish, sawfish-gnome and gnome-applets are also
missing. Most likely other packages are missing as well. I would like to
reiterate, WTF? -Jeff
On Saturday 14 April 2001 01:06,
dear all,
i just updated woody and klogd has disappeared into thin air.
it's not even in "dpkg -L sysklogd"
# dpkg -L "sysklogd" | grep klogd
/usr/share/doc/sysklogd
/usr/share/doc/sysklogd/changelog.gz
/usr/share/doc/sysklogd/copyrig
> "CF" == C Falconer <[EMAIL PROTECTED]> writes:
CF> I have this problem periodically on a P133 with a slightly
CF> screwey scsi root disk. It will mount / read-only, then many
CF> processes die due to being unable to write to disk.
Hmmthis _is_ a scsi drive, but it has not s
I have this problem periodically on a P133 with a slightly screwey scsi
root disk. It will mount / read-only, then many processes die due to being
unable to write to disk.
The sign is that / is mounted read-only, and that syslogd (which is still
running) says
scarf kernel: Last message repea
Quite serendipitously I discovered that the above processes had
stopped running on a potato system (i386) I have here. I noticed my
'locate' command did not seem to be returning good results, and when I
looked it was dated Oct 18. Then 'ps ax' told the Rest of the Story. A
reboot brought those thre
On Mon, 05 Jul 1999 18:59:44 GMT, you wrote:
>It looks like klogd on startup reads everything that is already in the
>kernel ring buffer and dumps it off to syslog before going to its
>normal operation mode.
Okay, now a different question. I see that not all boot messages are
written in
On Mon, 5 Jul 1999 15:25:44 +0100, you wrote:
>Quoting Marc Haber ([EMAIL PROTECTED]):
>> On Sun, 4 Jul 1999 13:14:46 -0700 (PDT), you wrote:
>> >On Sun, 4 Jul 1999, Marc Haber wrote:
>> >> I am curious. Where do I find the code that does this on Debian? I
>>
Quoting Marc Haber ([EMAIL PROTECTED]):
> On Sun, 4 Jul 1999 13:14:46 -0700 (PDT), you wrote:
> >On Sun, 4 Jul 1999, Marc Haber wrote:
> >> I am curious. Where do I find the code that does this on Debian? I
> >> grepped for klogd in /etc but did not find explicit code t
On Sun, 4 Jul 1999 13:14:46 -0700 (PDT), you wrote:
>On Sun, 4 Jul 1999, Marc Haber wrote:
>> I am curious. Where do I find the code that does this on Debian? I
>> grepped for klogd in /etc but did not find explicit code to do so.
>
>/etc/init.d/sysklogd
I fail to see where
Hi!
My Debian box seems to write the boot messages (that can be accessed
by dmesg) to the syslog on boot-up. The SuSE box at work has code to
dump this information to a file (/usr/sbin/klogd -f /var/log/boot.msg
-o) in /sbin/init.d/boot.
I am curious. Where do I find the code that does this on
Can you report the last 20 lines of your /var/log/klog ?
On Thu, Jul 01, 1999 at 05:20:53PM -0400, Peter Iannarelli wrote:
> Hello:
>
> I running potato with a 2.2.10 SMP kernel.
> I boot my system klogd used 99% of the CPU
> as reported by top.
>
> What could I be doing w
Hello:
I running potato with a 2.2.10 SMP kernel.
I boot my system klogd used 99% of the CPU
as reported by top.
What could I be doing wrong ? ( thats loaded )
Peter
begin:vcard
n:Iannarelli;Peter
tel;fax:1+ 416 929 1056
tel;work:1+ 416 929 1885
x-mozilla-html:FALSE
url:http://www.GenXl.com
24 matches
Mail list logo