>Another would be to create a lock on an SFS access directory, and then
>query the lock
SFS do not check the alternate user so the suggested method to
create a lock for a file to see what altuser is running do not
work if the worker it selves use any sfs files.
When the worker first access a filepool the appc connection is
assigned the userid/altuserid that the worker has in that moment
and that userid is kept in the sfs filepool as long as the appc
connection exists so even if the worker is assigned a new altuser
the connection to sfs still uses the old (firs) userid.
To get the “right” userid the worker has to reset the appc connection
to the filepool before accessing files for the new user.
This is a problem when developing worker applications using sfs,
the worker it selves can’t use files in sfs and the order of setting
up appc connections to sfs is very important.
Regards
Mats Westlund
