[syslog-ng] syslog-ng 3.1.2-1 problem/bug/?

[VDR User]

On Mon, Aug 16, 2010 at 5:54 AM, Balazs Scheidler <bazsi at balabit.hu> wrote:
> On Sun, 2010-08-15 at 20:14 -0700, VDR User wrote:
>> Hi.  I'm using Debian testing and "upgraded" from 3.1.1-3 to 3.1.2-1
>> earlier.  Now I'm getting "Error opening file for writing;
>> filename='/logs/vdr.log', error='Permission denied (13)'".. This
>> problem does _not_ occur with 3.1.1-3, which I have downgraded back to
>> (until the problem/bug is solved).  Are there any known issues causing
>> this?  I don't believe there are any permission problems considering
>> the user owns that dir and it works fine in 3.1.1-3.
>>
>> Following is the diff between the syslog-ng.conf's.  The - lines are
>> from my working 3.1.1-3 conf, the + lines are from the 3.1.2-1
>> conf....  Any help is appreciated.
>
> Hmm.. maybe the old version did use --no-caps and the new one doesn't?
>
> Ccing the Debian maintainer, maybe he knows about it.

Thanks for your reply.  After more investigation I've discovered that
3.1.1-3 was compiled with "Enable-Linux-Caps: off", while 3.1.2-1 was
compiled with "Enable-Linux-Caps: on".  After uncommenting
SYSLOGNG_OPTS="--no-caps" in /etc/default/syslog-ng, it is now working
correctly (as far as I can tell).  I noticed another behavior I do
believe is a bug however...  With 3.1.2-1 I see that ownership of
/logs (actually /usr/local/dvb/logs as /logs is a symlink pointing
there) was being changed to root/root.  I didn't tell syslog-ng to do
this, it just did it on it's own -- which I feel is unacceptable.  Is
there actually some sane reason I'm not thinking of that make
syslog-ng steal ownership of the pre-existing dir you're trying to
write a log file in?

Cheers,
Derek