Fuse will not start at boot time after a disorderly shutdown, because the stored PID matches a running process

Issue

After a disorderly shutdown -- server crash, power failure, VM termination -- Fuse will not restart. The failure can be quite clear if the administrator is trying to start Fuse at the prompt, but it is much less obvious if using init scripts or systemd unit files. Typically there will be a message that there is already a service running with the same process ID.