Re: NMU on sysklogd
On Fri, 2004-10-29 at 13:28 +0200, Javier Fernández-Sanguino Peña wrote:
> On Fri, Oct 29, 2004 at 11:56:46AM +0200, Jerome Warnier wrote:
> > In fact, I dug into the problem, and found that the initscript
> > (/etc/cron.daily/sysklogd) had a 'reload-or-restart' argument, which is
> > used by the cronjob and does not always work (in my case, on several
> > machines, never) nor do the restart one (I'm not sure anymore I tried
> > it, though). So, I replaced the last line:
>
> (...)
>
> I think it would be best if you sent this information to the BTS, as a
> patch for the current package. That way others (including the maintainer,
> which needs not be following this thread) can test it too.
Well, the problem is that I'm not happy with that solution. In fact, the
initscript should be fixed, which maybe involves bug #211858 (relates to
--pidfile), which has already a non-applied patch.
The fact is that both 'reload-or-restart' and 'restart' do not work as
expected.
> Please provide as much information in order to reproduce this issue as
> possible too.
It is very simple: install a Sarge, let it run and you'll see at some
point that /var/log/syslog (this is not the only file affected of
course) is empty and keeps empty and syslog.0 continues to be filled by
the new messages.
All my Sarge systems show the same behaviour.
> Those are the very first steps you should take before even considering a
> NMU. Also, in this particulary case, read the README.NMU file in the
> sources.
I cannot do a NMU myself, so don't worry, I won't ;-)
> I've been reviewing these packages' bugs. Even if some patches could be
> introduced to fix some of the issues I'm not sure all of them are
> appropiate. Even so, this package is of base priority, so it's frozen in
> sarge, only RC bugs should be fixed there. Maybe a cleanup of the package
I'm aware of that too.
> could be considered (following the NMU procedures above) and I'm open to
> doing it myself (as I've been doing it for other base packages).
Well, thanks but it is not quite ready for that.
> I haven't yet contacted Joey, however, since I'm still considering this
> option and how to do it best. One option, for example, is to do a NMU to
> experimental so other people can test the package (and verify that the bugs
> are actuall fixed) before uploading to sid. I have done this for other base
> packages (like ifupdown). I suggest you think about it (and the
> consequences of a broken^Wuntested upload at this point) before talking
> with him.
We'll see that in due time. I have lots of other things to do.
> Regards
>
> Javier
--
Jerome Warnier <jwarnier@beeznest.net>
BeezNest s.a r.l.
Reply to: