Am 14.07.2014 um 16:47 schrieb Forrest Pruitt:
The frustrating thing is that in a stand-alone python shell, pycuda
behaves appropriately. It is only in a Celery process that things
break down.
Any help here would be appreciated!
If I need to provide any more information, just let me know!
This reeks of a permission issue. Check which users have access to
/dev/nv*, and make sure that the user that Celery runs as also has
access to those devices.
Hope that helps,
Andreas
_______________________________________________
PyCUDA mailing list
PyCUDA@tiker.net
http://lists.tiker.net/listinfo/pycuda
