[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Problem with DLLs

We've had problems with some off-the-shelf apps requiring a fuller user profile than Win32 Condor provides - try getting a Condor job to return env variables (set > set.txt) to see an example of the reduced environment. We never solved this one and now discourage our users from trying it :-( For more notes on this matter search this lists archives for posts from my colleague 'SG Wilkinson' - there are six in March and April 2005.

We do have compiled Matlab working fine in this manner though. Matlab DLLs are accessed from a RO network share Condor jobs can connect to using a batch wrapper around their exe. Some crazy users also had some success using Cygwin this way to!


--On 26 April 2006 14:34 +0100 "Dr Ian C. Smith" <i.c.smith@xxxxxxxxxxxxxxx> wrote:

--On 26 April 2006 12:42 +0100 "Dr Ian C. Smith"
<i.c.smith@xxxxxxxxxxxxxxx> wrote:

Incidently I'm seeing exactly this problem when I try to run SRB clients
using Condor. Empty stdout and stderr and the same logfile message as
you. When I run the same .exe's under my own account (which is
non-priviledged) it's fine. Bizarre !

I meant that when I run them *interactively* they work. When I change the
VM1_USER attribute to run the condor job under my account (with a
previously stored cred) they fail as well.

Condor-users mailing list

Patrick Townsend  -  Computer Support
Electrical  &  Electronic Engineering
MVB room 4.27   University of Bristol
www.bris.ac.uk     Tel: 0117 954 5288
email: patrick.townsend@xxxxxxxxxxxxx