<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 12.800000190734863px; background-color: rgb(255, 255, 255);" class="">If I run several sbcl processes on different nodes in my compute cluster, it might happen that two different runs notice the same file needs to be recompiled (via asdf),</span><div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 12.800000190734863px;" class="">and they might try to compile it at the same time. What is the best way to prevent this?</div><div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 12.800000190734863px;" class=""><br class=""></div><div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 12.800000190734863px;" class="">I see in the asdf documentation that there is an asdf:*user-cache* variable whose</div><div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 12.800000190734863px;" class="">value is the path name of the directory where asdf compiles into. Would it be advisable for my to arrange so that asdf:*user-cache* is a function of the pid and hostname and perhaps thread-id (if such a thing exists) to avoid such collisions?</div><div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 12.800000190734863px;" class=""><br class=""></div><div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 12.800000190734863px;" class="">Or is there some better way to handle this which is build into asdf?</div></body></html>