On Thu, May 25, 2006 at 01:49:20AM -0500, Manoj Srivastava wrote:
The maintainer, at some point during a private conversation, even
discouraged me to upload to *experimental* a new version of sysklogd
fixing the issues I have prepared. That's why they ended up in my
p.d.o page (they are
On Tue, May 23, 2006 at 09:52:02PM -0500, Manoj Srivastava wrote:
Actually, from personal experience, bugs are not fixed because the
maintainer is against all NMUs, even those that follow the steps
described in the sysklogd's source 'debian/NMU-Disclaimer'. The
current maintainer's
Javier Fernández-Sanguino Peña quoted:
These rules always apply. They even apply if somebody declares NMUs
as ok and reduces regular NMU rules to a delay of zero days. Unless
I'm on vacation or on a show I am reachable via mail, so there is
hardly a reason not to contact me.
Hmm, this
On 24 May 2006, Javier Fernández-Sanguino Peña verbalised:
On Tue, May 23, 2006 at 09:52:02PM -0500, Manoj Srivastava wrote:
Actually, from personal experience, bugs are not fixed because the
maintainer is against all NMUs, even those that follow the steps
described in the sysklogd's source
[Nathanael Nerode]
Conclusion
--
We should change the default syslogd.
There is only one feature I miss in the current sysklogd package, and
that is the ability to store the facility and severity in the log
file. If we are to switch, please select one where this is possible
to
On 23 May 2006, Javier Fernández-Sanguino Peña said:
On Sun, May 21, 2006 at 07:38:10AM -0400, Nathanael Nerode wrote:
(...)
Issues: (1) Quality. sysklogd has 105 open bugs: 3 important (1
with patch), 43 normal (11 with patches), 11 minor (4 with
patches), and 19 wishlist (some of which
* Florian Weimer ([EMAIL PROTECTED]) wrote:
* Nathanael Nerode:
(2) Upstream status.
There hasn't been a new upstream for sysklogd since 2001.
All of the others are active upstream.
Have you checked if SuSE's syslog-ng is heavily patched? If it's
mostly alright, it's probably a good
On Sun, May 21, 2006 at 07:38:10AM -0400, Nathanael Nerode wrote:
(...)
Issues: (1) Quality.
sysklogd has 105 open bugs: 3 important (1 with patch), 43 normal (11 with
patches), 11 minor (4 with patches), and 19 wishlist (some of which are
really quite important, such as 44523)
Please, when
OK, I brought this up a while back. (For some reason I can't seem to find the
beginning of the topic, but see
http://lists.debian.org/debian-devel/2006/01/msg00238.html )
I got a few comments in favor.
Someone asked what syslog other distros are using. RedHat is still using
sysklogd.
However,
Nathanael Nerode wrote:
[snip]
The installer can use whatever seems most appropriate (does it even log?):
The installer does log and puts the logs at /var/log/debian-installer/ on
the successfully installed system. If the installation fails, the logs (in
the installer ramdisk) are a valuable
* Nathanael Nerode:
(2) Upstream status.
There hasn't been a new upstream for sysklogd since 2001.
All of the others are active upstream.
Have you checked if SuSE's syslog-ng is heavily patched? If it's
mostly alright, it's probably a good indicator that syslog-ng is the
way to go (and I
11 matches
Mail list logo
