Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CLI switch to disable use of file locking #1759

Open
a-ludi opened this issue Aug 22, 2019 · 0 comments
Open

Add CLI switch to disable use of file locking #1759

a-ludi opened this issue Aug 22, 2019 · 0 comments
Labels

Comments

@a-ludi
Copy link

a-ludi commented Aug 22, 2019

System information

  • DUB version 1.15.0
  • Lustre file system without file locking

Bug Description

It is currently not possible to use DUB if the package cache is located on a file system that does not implement file locking.

Expected Behavior

In order to support these file systems, a CLI switch --no-lock should be added which disables file locking but not the lock file itself. When the switch is in effect DUB will still check if the lock file is present or create it otherwise. Even though this might lead to race conditions, it is the best options if file locking is not supported.

There might be a better name for the switch because --no-lock suggests not even a lock file being created/checked.

An alternative to the CLI switch would be to dynamically check if file locking is supported and decide for the safest locking strategy available.

@Geod24 Geod24 added the bug label Dec 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants