I've spent quite a bit of time cleaning up dpb.

I've fixed a few minor bugs (by minor, it's stuff you shouldn't
even notice, hopefully)

I now try much harder to clean up on impromptu exit, so that there
should no longer be orphaned processes around.

Anyway, I've added a new feature to the external socket control:

wipe fullpkgpath

this allows cleaning up an errored out fullpkgpath on the correct
host, THEN removing the lock/affinity, so that dpb will try again.

That's a feature I wanted to have for a long time, because usually
some port break, I do a cvs update, notice the port was updated,
then hunt the right host, do the cleanup manually, wait for rm -rf
to finish, THEN remove the lock, forget about the affinity so it
will restart on the same host... which is time consuming when
handling day-to-day issues.

Reply via email to