Bug 895307

Summary: ngircd ignores SyslogFacility configuration option
Product: [Fedora] Fedora EPEL Reporter: CJ Kucera <pez>
Component: ngircdAssignee: Andreas Thienemann <andreas>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: el6CC: andreas, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-19 22:13:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Updated patch to fix the issue none

Description CJ Kucera 2013-01-15 02:42:36 UTC 
Created attachment 678558 [details]
Updated patch to fix the issue

The option "SyslogFacility" in the "[Options]" section of ngircd's config file is supposed to be able to tell ngircd where to log.  (That option isn't included in the sample config file, but it is mentioned in ngircd.conf(5).)  Syslog is set up before the conf file is read, though, and the configured facility is never actually used - logs just go to the default facility.

It turns out that bug was discovered in February 2012: http://arthur.barton.de/pipermail/ngircd-git-ml/2012-February/000907.html

The actual git commit for a fix is at their repo is here: http://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd.git&a=commit;h=3641e511095203818df7ca05439cf42eb7c7c954

That patch doesn't apply directly without some fuzziness which %patch0 doesn't seem to like, so I'll attach an updated patch which applies cleanly to ngircd-18.  Perhaps it'd make sense to just update ngircd to its latest version instead (it's at 20.1 now).  If I get some more time I'll see about submitting an updated .spec for that.
Comment 1 CJ Kucera 2013-01-15 06:18:10 UTC 
Okay, well - after some preliminary testing, it looks like ngircd v20.1 works just fine with the current .spec file (with just the version number change).  I haven't used it too much, but v20.1 does fix this bug.
Comment 2 Kevin Fenzi 2013-02-03 01:21:14 UTC 
Yep. Sorry for the delay here. 

I will be pushing a 20.1 out here in a bit. testing very welcome...
Comment 3 Fedora Update System 2013-02-03 01:31:18 UTC 
ngircd-20.1-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/ngircd-20.1-1.el6
Comment 4 Fedora Update System 2013-02-05 01:30:33 UTC 
Package ngircd-20.1-1.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing ngircd-20.1-1.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-0254/ngircd-20.1-1.el6
then log in and leave karma (feedback).
Comment 5 Fedora Update System 2013-02-19 22:13:07 UTC 
ngircd-20.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.