Standby Fuse container in active/standby configuration does not expose an SSH service since 6.2

In Fuse 6.1, when Fuse was used in an active/standby configuration so that only one instance would be active at a given time, the standby instance initialized its SSH service and could be interrogated via SSH or using the bin/client script.

As of 6.2 this behaviour has changed, presumably because the start-level of the sshd bundles have changed from 30 to 80. Customers that relied on SSH access to monitor their production systems can no longer do so.