Puppy Linux Discussion Forum

puppy_ok · Joined: 05 Oct 2006 Posts: 12

how to disable forever syslogd and klogd daemon?
at boot is automatic enabled.
please help me Smile

GuestToo · Puppy Master Joined: 04 May 2005 Posts: 4078

put in /etc/rc.d/rc.local:

killall klogd syslogd

BarryK · Posted: Sat 07 Oct 2006, 19:00 Post subject:

They are started in /etc/rc.d/rc.sysinit, so you can just comment-out the lines.

I was wondering about these recently also. Do we really need them?
Do they slow things down much? Any disadvantages to having them running?

GuestToo · Puppy Master Joined: 04 May 2005 Posts: 4078

i guess the error messages are useful for diagnostic purposes

i think "puppy_ok" wanted them stopped because they kept accessing the hard drive and causing it to keep spinning

if you let them run while Puppy is booting, then kill them in rc.local or somewhere, you get the error messages while Puppy is booting, and they are shut down later when they may not be needed

a lot of programs (for example, iptables) use syslogd for logging messages

azstew · Posted: Mon 01 Oct 2012, 14:02 Post subject: syslogd -m 0 hogs cpu

At boot it starts, and uses 60-70% of cpu and I have to kill it.

Problem just started today. Puppy 5.2.5, 2 GB RAM, frugal install on SDHC, 1.6 Atom processor.

Here are the files I believe control syslogd and klogd

etc/rc.d/rc.sysinit

line 28 #100126 move syslogd, klogd to /etc/init.d/00sys_logger
line 307 #100126 moved to /etc/init.d/00sys_logger...
line 308 #syslogd -m 0
line 309 #klogd

/etc/init.d/00sys_logger (contents of file)

#!/bin/sh

case $1 in
start)
syslogd -m 0
klogd
;;
stop)
killall klogd
killall syslogd
;;
esac

How can I keep them from starting/are they needed?

Karl Godt · Joined: 20 Jun 2010 Posts: 3956 Location: Kiel,Germany

The files in /etc/init.d/* are started by /etc/rc.d/rc.services . That script should check if a file is executable in /etc/init.d/* and if not executable like README files , should skip them .