Often, users when running workflows in glite mode are submitting them to a local campus cluster where there is no remote file server available. there is support for Glite in pegasus that works well for sharedfs deployments.

however, for nonsharedfs deployments workflows only work if the pegasus generated auxillary jobs run locally. that is often not the case, as users have file server urls ( file:/// ) in their site catalog for the clusters. In that case, the planner generated submit files are incorrect. a fix for this involves the auxiliary jobs to be launched via PegasusLite also ( at least for the remote case)