30 Oct 2007 16:52
Re: RC Problem with klog and syslogd
1-IT-4-HOSP <1-it-4-hosp <at> auswaertiges-amt.de>
2007-10-30 15:52:34 GMT
2007-10-30 15:52:34 GMT
Hi, Amon Ott schrieb Am 27.10.2007 18:47: > So klogd (pid 1985) sends data to syslogd (pid 1975) through Unix > socket /dev. Two things that look wrong: > > - Path should usually be /dev/log (is /log correct in your system?) > - The RECEIVE request should show the other process 1985 as partner > process (value of attribute "process"). This may be caused by > sys_sendto, where the receiver does not see the sender's pid. > "/log" is _not_ correct in my system. It's the default directory "/dev/log" and I don't see the reason why the messages says "/log". I tried to start "syslogd" with the parameter "-p /dev/log" to force "syslogd" to use "/dev/log", no changes. Then I tried "strace -f syslogd", but it says that it uses "/dev/log" (than it's unlinked by the -p parameter and again set to "/dev/log"), so that looks right for me. > First of all, you should enable RC debugging to see the exact role and > type involved. Either use rsbac_debug_adf_rc kernel parameter, or as > user 400 (secoff) call: > > echo debug_adf_rc 1 >/proc/rsbac-info/debug > done. > Depending on your setup, klogd's and syslogd's role are either 999999 > (boot role) or 2 (root's role). The RC type of /log is 0 by default. > Which "setup" do you mean? The "make menuconfig" before compiling? > Let us assume the role is 2. Then as user 400 call(Continue reading)
Should I disable "Check partner process" with the next version I compile?
Dustin
RSS Feed