You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The POD in PAR.pm mentions PAR_CLEAN but setting an environment variable with that name to 1 on Windows 7 did not appear to have any effect. Setting PAR_GLOBAL_CLEAN to 1 had mostly the desired effect of cleaning up the cache, so I suspect that where the POD mentions PAR_CLEAN it should mention PAR_GLOBAL_CLEAN instead.
Setting PAR_GLOBAL_CLEAN had mostly the desired effect because afterwards a file 6b952d69.xs.dll of 19 kB in size remained in the par-/temp- directory. After multiple runs that file had the same name (but in different temp- directories). The clean-up code is not entirely successful.
The POD describes the cache location (with cleaning) as TEMP/par-USER/temp-PID/ and describes USER as being "the user name", but in my experience it is some hash value -- perhaps a hash of my user name.
Regards,
Louis Strous
The text was updated successfully, but these errors were encountered:
The POD in PAR.pm mentions
PAR_CLEAN
but setting an environment variable with that name to 1 on Windows 7 did not appear to have any effect. SettingPAR_GLOBAL_CLEAN
to 1 had mostly the desired effect of cleaning up the cache, so I suspect that where the POD mentionsPAR_CLEAN
it should mentionPAR_GLOBAL_CLEAN
instead.Setting
PAR_GLOBAL_CLEAN
had mostly the desired effect because afterwards a file 6b952d69.xs.dll of 19 kB in size remained in the par-/temp- directory. After multiple runs that file had the same name (but in different temp- directories). The clean-up code is not entirely successful.The POD describes the cache location (with cleaning) as
TEMP/par-USER/temp-PID/
and describesUSER
as being "the user name", but in my experience it is some hash value -- perhaps a hash of my user name.Regards,
Louis Strous
The text was updated successfully, but these errors were encountered: