| Summary: | app-admin/sysklogd-1.5-r2: improve default syslog.conf to match syslog-ng.conf behavior | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | trivial | CC: | bkohler, mr_bones_ |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | syslog.conf.patch | ||
np by me, but i don't use sysklogd But it's a strange idea that every logger needs to act like syslog-ng out of the box. You could just... use syslog-ng, right? Let's say I am used to have the messages on VT12. Otherwise have to do "less /var/log/messages" all the time. ;-) More seriously. Why couldn't be equivalent packages preconfigured to give same output, when possible? I see no reason to diverge from what upstream is shipping. If you wish for all packages to be ruthlessly modified to conform to a specific view, Redhat/Fedora is a better bet. |
Created attachment 300751 [details, diff] syslog.conf.patch I was a bit unhappy that on VT12 there was no output I used to see with syslog-ng. How about changing the default file to adjust the behavior more to syslog-ng?