On Sat, Jul 11, 2026 at 08:52:16AM -0400, Greg Wooledge wrote:
> On Sat, Jul 11, 2026 at 06:59:14 +0200, [email protected] wrote:
> > so in your case it is
> > 
> >   /var/lib/dpkg/info/vrfydmn.prerm
> > 
> > One way to get out of that is to insert at the top of that script
> > an "exit 0", which makes the script always succeed, then try your
> > 
> >   dpkg --purge vrfydmn
> > 
> > (same for your other package).
> > 
> > BTW: if anyone knows a more elegant "knob" for that, I'd like to
> > know :-)
> 
> No, that's been the standard advice for broken init.d scripts for
> many years now.

Thanks for confirming!

> Of course, I would accompany that by telling the OP
> to find any vrfydmn processes and kill them manually, which is what
> the init.d script should have done.

Or just wait to the next reboot: no init script -> no restart
(I know, I know :)

> The only other advice you can give is "debug the init.d script so
> that it works", which is usually beyond the abilities of the people
> asking these questions.

Note that I just recommended short-circuiting the pre-remove, thus
bypassing the init script altogether...

Cheers
-- 
t

Attachment: signature.asc
Description: PGP signature

Reply via email to