FileMonitoringTask currently assumes that the caller of the task owns an exclusive lock on the workspace. For some purposes this is not a safe assumption, so it should instead generate distinct tracker files for each concurrent invocation.