Case 7355: Encode the scheduler name in the cluster file on disk to avoid file clashes
Case 7355: Encode the scheduler name in the cluster file on disk to avoid file clashes

Without the scheduler name included in the file name it's possible that duplicate cluster IDs will occur for a multi-scheduler machine which would would mean proxy submission .cluster files would clash.

cyclecomputing/condor-agent,cyclecomputing/condor-agent