Your message dated Fri, 8 Dec 2006 00:19:01 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Closed by 2.9012.497-4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: general
Version: 20010605
Severity: normal
hello,
I report this bug against general because I'm not sure against which package I
should
report it. init ?
Here is the story: First, I have to say that I've made the first error, but it
was a
bad surprise to see that Debian can't handle the problem correctly. I've send a
signal STOP
to the distributed-net daemon to retrive my full CPU for some reson. Then, I've
rebooted
the system. Naturally, the /etc/init.d/distributed-net script freezed while
trying to kill
it and waiting it to die. I had to do a hardware boot.
So, here is my request: Debian should be able to timeout the scripts in
/etc/init.d in some way
I think it should be made in init (and so, the bug should be reassigned to it),
but I'm not
sure.
Sorry for this pretty vague repport, but I'm not sure how my problem could be
solved...
Bye, Mt.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux pixies 2.2.17-ide #1 Sat Sep 9 14:03:23 EST 2000 i686
unknown
--- End Message ---
--- Begin Message ---
These bugs should have been closed by the upload for version 2.9012.497-4.
This version was physically uploaded at the same time as 2.9013.498-1, which
appears to cause bugs not listed in the "newest" changelog entry to not be
closed. This was a mistake on my part.
See the changelog for the details.
James
--- End Message ---
