Skip to content

quicklisp does not lock system-index.txt file #178

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

Open
guicho271828 opened this issue Feb 16, 2019 · 1 comment
Open

quicklisp does not lock system-index.txt file #178

guicho271828 opened this issue Feb 16, 2019 · 1 comment

Comments

@guicho271828
Copy link

When two processes run in parallel, valious asdf-related calls (e.g. system-relative-pathname in my case) simultaneously tries to delete system-index.txt.bak which fail because another process has already deleted it.
Candidate solutions:

  • Take some form of file lock on system-index.txt
  • Ignore the error and just ensure the backup file is deleted
  • Name the backup file with a hash value to minimize the collision
@guicho271828
Copy link
Author

I've run into this problem on a compute cluster running on IBM GPFS[1] but it would not be the cause of the problem.
[1] https://www.ibm.com/support/knowledgecenter/en/SSPT3X_3.0.0/com.ibm.swg.im.infosphere.biginsights.product.doc/doc/bi_gpfs_overview.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant