Summary: | app-admin/syslog-ng: is "threaded(yes)" a good choice for the delivered config files ? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | [OLD] Server | Assignee: | Mr. Bones. (RETIRED) <mr_bones_> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | bkohler, mplichta |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=406623 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
![]() This may be related to bug 406623 which appears to have been fixed in 3.6.2 (In reply to Ben Kohler from comment #1) > This may be related to bug 406623 which appears to have been fixed in 3.6.2 yes, but as long as 3.4 is stable ... (and I tried 3.6.2 and switched back to stale due to terrible/wrong timestamp jumps/bugs of 3.6.x Right, I'm thinking maybe the other one should be reopened. The rationale for closing it was "Unless some bug shows up, syslog-ng-3.6.1 will go stable in ~30 days." ...and that was 90 days ago. Or maybe this bug could convert into a stablereq with appropriate deps & blockers to keep track of things. yes, threaded(yes) is a good default. It is in fact enabled by default by upstream. This is really the kind of thing that belongs in an email rather than a bug report. |