Matthew Heon d2b77f8b33 Do not make renumber shut down the runtime ...

The original intent behind the requirement was to ensure that, if
two SHM lock structs were open at the same time, we should not
make such a runtime available to the user, and should clean it up
instead.

It turns out that we don't even need to open a second SHM lock
struct - if we get an error mapping the first one due to a lock
count mismatch, we can just delete it, and it cleans itself up
when it errors. So there's no reason not to return a valid
runtime.

Signed-off-by: Matthew Heon <matthew.heon@pm.me>

2019-02-21 10:51:42 -05:00

..

shm

Recreate SHM locks when renumbering on count mismatch

2019-02-21 10:51:42 -05:00

in_memory_locks.go

Do not make renumber shut down the runtime

2019-02-21 10:51:42 -05:00

lock.go

Do not make renumber shut down the runtime

2019-02-21 10:51:42 -05:00

shm_lock_manager_linux.go

Do not make renumber shut down the runtime

2019-02-21 10:51:42 -05:00

shm_lock_manager_unsupported.go

Add initial version of renumber backend

2019-02-21 10:51:42 -05:00