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

.lock files left behind in PERL_INLINE_DIRECTORY #38

Closed
anthonybakermpls opened this issue Mar 18, 2015 · 2 comments
Closed

.lock files left behind in PERL_INLINE_DIRECTORY #38

anthonybakermpls opened this issue Mar 18, 2015 · 2 comments

Comments

@anthonybakermpls
Copy link

After a perl script builds inline CPP, a .lock file is left over in the PERL_INLINE_DIRECTORY under the username of the running user. This prevents subsequent runs by other users who share the same PERL_INLINE_DIRECTORY and cannot delete the lock file left over. We are seeing this on Red hat linux with perl version 5.20.2, inline:CPP version 0.71, Inline::C 0.74. The Inline CPP folks are directing me to Inline and/or Inline::C. See daoswald/Inline-CPP#29 . The issue goes away after removing file locking code in Inline::CPP - CPP.pm lines 681,682 even though no lock file with a .lock signature is being created at that point (from David's investigation/understanding).

@anthonybakermpls
Copy link
Author

Bah, sorry meant to submit to Inline. I don't know if this is Inline or Inline::C at this point.

@mohawk2
Copy link
Collaborator

mohawk2 commented Mar 18, 2015

@anthonybakermpls, not to say this is your problem to fix, but if you do a search in Inline's lib/Inline.pm, you'll find calls to flock(). Can you experiment with those?

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

2 participants