This bug was fixed in the package busybox - 1:1.1.3-5ubuntu10
---
busybox (1:1.1.3-5ubuntu10) hardy; urgency=low
[ Matt T. Proud ]
* Patch syslogd remote logging implementation to behave actually like
sysklogd when the destination host cannot be reached or resolved. In
oth
I just needed to get time to get round to my sponsorship queue, that's
all. I'm working on this now; it looks good to me. Thanks!
--
BusyBox's Syslog Remote Logging Implementation Does Not Behave Like Actual
Sysklogd with Least Effort Delivery Behavior
https://bugs.launchpad.net/bugs/184126
You
Hi,
In addition to #184130, is there anything that I can do to help expedite
this bug's processing? Is it likely to be incorporated into Hardy before
the forthcoming code freeze?
Thanks,
Matt
--
BusyBox's Syslog Remote Logging Implementation Does Not Behave Like Actual
Sysklogd with Least Eff
** Changed in: busybox (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Colin Watson (kamion)
Status: New => Confirmed
--
BusyBox's Syslog Remote Logging Implementation Does Not Behave Like Actual
Sysklogd with Least Effort Delivery Behavior
https://bugs.launchpa
One thing that I forgot to note: Launchpad bug #178270 may be closed, as
this one supersedes it.
** Attachment added: "BusyBox Remote Syslog Behavior Conformance Patch for
Hardy Heron."
http://launchpadlibrarian.net/11432250/busybox-syslog-behavior-conformance.patch
--
BusyBox's Syslog Remo
