Comment 3 for bug 963565

The question is why was pkcsslotd still running... I'd expect the prerm to stop it and postinst to start it, making the only failing case happen if someone manually starts it at the middle of the upgrade.

Is that a case where "stop" doesn't actually stop pkcsslotd?
I did a few tests here and it seems to always stop/start reliably and return 0 as expected (unless you start it twice).

An easy workaround is to make the init script return 0 if the daemon is already running but I'm not sure returning 1 in that case is really wrong.