* Steinar H. Gunderson ([EMAIL PROTECTED]) wrote: > Please let me know ASAP if you have any objections; I'll be asking the RMs > what's a reasonable delay for an NMU fixing problems introduced in my own > NMU, but I guess I'll be able to upload sometime tomorrow.
It fixes RC bugs and therefore should have the associated severity. I
don't see that it being an NMU of an NMU changes that. I'd also rather
have the reduced delay than the init script or associated patches.
I'm not convinced the logic for working with the delays is entirely
correct though (and does what it claims) so I wanted to test with some
different settings to ensure correct behavior.
In general, my goal would be a 1-2s delay per NSS call and then see how
that affects the boot process. Or perhaps even no delay on an immediate
connect() failure (due to closed port or something) provided at least 2
attempts were made. Again, it depends on how it impacts a normal boot
process and that depends on the number of NSS calls made.
Additionally, I don't think 'update-rc.d remove' will correctly preserve
modifications done to the init process by the user which is incorrect
behaviour.
Enjoy,
Stephen
signature.asc
Description: Digital signature
