View Issue Details

IDProjectCategoryView StatusLast Update
0004562unrealircdpublic2016-01-30 10:48
Reportermagic000 Assigned Tosyzop  
Status resolvedResolutionfixed 
OSFreeBSD OS Version10.2 
Product Version4.0.1 
Fixed in Version4.0.2 
Summary0004562: Error logging using system syslog is not possible
DescriptionRunning 3-series it was enough to specify "syslog" instead of a filename under the log block to have error messages sent to system's syslog. This is not longer working so in 4.0.1. The process simply creates a filename called "syslog" (under logs/) and writes error messages to it. No communication with syslog is attempted.
Steps To ReproduceRunning 4.0.1 as usual. Run in a FreeBSD 10.2 jail.
Additional InformationThis is a crucial feature for me. Being able to specify a syslog facility and level (e.g. to have sent the logs to local0.notice) would be also most welcome.

Alternatively, you could consider handling syslog the way nginx does, i.e. so error messages of any facility and level can be sent to a remote syslog directly.
TagsNo tags attached.
3rd party modules


related to 0004563 acknowledged Specify syslog facility and level 



2016-01-30 10:48

administrator   ~0019080

Ah, I see what's going on.. it's converting "syslog" to an absolute path, resulting to logging to a file, as you mentioned.

This is now fixed. Thanks for the report.

I've spun off your request regarding syslog facility/level/more to 0004563.

Issue History

Date Modified Username Field Change
2016-01-30 10:27 magic000 New Issue
2016-01-30 10:43 syzop Issue cloned: 0004563
2016-01-30 10:43 syzop Relationship added related to 0004563
2016-01-30 10:48 syzop Note Added: 0019080
2016-01-30 10:48 syzop Status new => resolved
2016-01-30 10:48 syzop Fixed in Version => 4.0.2
2016-01-30 10:48 syzop Resolution open => fixed
2016-01-30 10:48 syzop Assigned To => syzop