Re: [PATCH] fix syslog corruption when using customized name

2016-10-31 Thread Chris Caputo
On Mon, 31 Oct 2016, Ondrej Zajicek wrote: > On Sun, Oct 30, 2016 at 10:40:30PM +, Chris Caputo wrote: > > Fix bug with syslog using string passed to openlog() which is later > > stomped on, resulting in corrupted log messages. This happens when name > > is specified in a syslog log line, ala:

Re: [PATCH] fix syslog corruption when using customized name

2016-10-31 Thread Ondrej Zajicek
On Sun, Oct 30, 2016 at 10:40:30PM +, Chris Caputo wrote: > Fix bug with syslog using string passed to openlog() which is later > stomped on, resulting in corrupted log messages. This happens when name > is specified in a syslog log line, ala: Thanks, you are right. I will merge the patch. No

[PATCH] fix syslog corruption when using customized name

2016-10-30 Thread Chris Caputo
Fix bug with syslog using string passed to openlog() which is later stomped on, resulting in corrupted log messages. This happens when name is specified in a syslog log line, ala: log syslog name "bird-foo" all; Per Linux SYSLOG(3): The argument ident in the call of openlog() is probably sto