Running cluster with the wrong configuration path gives misleading error

[hsanjuan]

[16:22:47] ~ $ ipfs-cluster-service -c c2
16:23:09.941 ERROR    service: could not obtain execution lock.  If no other process
is running, remove /home/hector/c2/cluster.lock, or make sure that the config folder is
writable for the user running ipfs-cluster.  Run with -d for more information
about the error lock.go:37
error acquiring execution lock: could not obtain execution lock

The locking attempt should probably say something like the "folder does not exist" and ask the user to check that the cluster is correctly initialized in the given location.

[lanzafame]

@hsanjuan Just to clarify, what was the correct resolution to the problem?

[hsanjuan]

@lanzafame the locking code should realize that the folder does not exist and just inform about that, rather than suggesting that there is other cluster process running.