syslog-ng problem description(again)

From: Bencsath Boldizsar <boldi@datacontact.hu>
Subject: syslog-ng problem description(again)
Date: Thu, 12 Apr 2001 19:05:51 +0200 (CEST)

Next Article (by Date): Re: syslog-ng problem description(again) SZALAY Attila
Previous Article (by Date): rsbac-v1.1.2-pre2 uploaded Amon Ott
Next in Thread: Re: syslog-ng problem description(again) SZALAY Attila
Articles sorted by: [Date] [Author] [Subject]

So the exact problem was the following, who missed it:

syslog-ng doesn't start if a unix socket soruce exists in the config file
(
source src { unix-stream("/dev/log"); internal(); file("/proc/kmsg"); };
)

strace:

[pid 14144] unlink("/dev/log")          = -1 ENOENT (No such file or
directory)
[pid 14144] bind(4, {sin_family=AF_UNIX,
path="                                                                                                    /dev/log"},
110) = -1 EPERM (Operation not permitted)

(Apr 12 19:02:24 db rsbac_adf_request_rc(): rsbac_get_attr() returned
error -1017!
Apr 12 19:02:24 db rsbac_adf_request(): request READ_WRITE_OPEN,
caller_pid 15361, caller_prog_name syslog-ng, caller_uid 0, target-type
IPC, tid ???-ID 134521299, attr sockaddr, value 3437575888, result
NOT_GRANTED by RC)

Two problems: why has the bind command 110 bytes path attribute, why not
only "/dev/log".

But: However why does rsbac stops at such ipc requests.
workaround: delete unix-stream from the syslog-ng config file.

problem on:
2.4.3+rsbac 1.2.1 pre 1 , 1.1.1, 
no problem on emergency kernel (I'm not really sure cause at one boot it
said there is some problem but after that it worked)

with:
syslog-ng (potato,unstable) in debian, and syslog-ng 1.4.11 and 1.5.5a
from source

boldi


-
To unsubscribe from the rsbac list, send a mail to
majordomo@rsbac.org with
unsubscribe rsbac
as single line in the body.

Go to Compuniverse LWGate Home Page.