Using the same signoff for the same resource at the doesn't cause an error.

[pgagne]

This would seem like more of a feature then a bug, but the main issue is it is inconsistant with the documentation and expected behavior of a signoff string.

Did the following test:

client1> rlock --lock --search-string aws-resource-1 --signoff hold1

client2> rlock --lock --search-string aws-resource-1 --signoff test-so-1

client3> rlock --lock --search-string aws-resource-1 --signoff test-so-1 

I would of expected an error on client 3 about using a signoff string that is already in use. I found that if I tried to lock a different resource (saw aws-resource-2) I did get an error.

When i released hold1 signoff client2 got the lock, released that one, client3 got it.

If this is the behavior we want we should document it as such. Otherwise we should throw an error when it happens.