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

Belpeople insist on grabbing GPU lock with no GPU hardware and GPU-off flags #126

Open
ribasushi opened this issue Nov 4, 2020 · 2 comments

Comments

@ribasushi
Copy link

I am running a lotus miner on a GPU-less machine with:
BELLMAN_NO_GPU=1 lotus-miner run --enable-gpu-proving=false

Regardless I still get /tmp/bellman.gpu.lock being exlock-ed ( discovered due to incorrect permissions on said file leading to sealing failures )

Bellperson should not do GPU-related things when told not to.

@ribasushi
Copy link
Author

fml... there's also /tmp/bellman.priority.lock

@porcuquine
Copy link

General lock is for use of the GPU. Priority lock is to kick lower-priority processes off the GPU. Why do we lock when no GPU being used? Great question. How about 'historical reasons'. This will probably see change in the 'relatively near future'.

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