Hi Chris, > Unfortunately it looks like the license request information doesn't get > propagated into any prologs from what I see from a scan of the > documentation. :-(
Thanks. If I am reading you right, I did notice the same thing and in fact that's why I wrote that job_submit lua script which gets the license information and sets an environmental variable, in the hope that such a variable would be inherited by the prolog script. But if I understand correctly your Prolog vs TaskProlog distinction, the latter would have the environmental variable and run as user, whereas the former runs as root and doesn't get the environment, not even from the job_submit script. The problem with a TaskProlog approach is that what I want to do (making a non-accessible file available) would work best as root. As a workaround is that I could make that just obscure but still user-possible. Not ideal, but better than nothing as it is now. Alternatively, I could use another way to let the job_submit lua script communicate with the Prolog, not sure exactly what (temp directory on the shared filesystem, writeable only by root??) Thanks for pointing to that commit. I bit too down the road but good to know. Cheers, Davide
