[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Condor-users] Condor.pm - log path since 672 only relative?
- Date: Thu, 31 Mar 2005 10:06:35 -0600
- From: "Bill Taylor" <bt@xxxxxxxxxxx>
- Subject: RE: [Condor-users] Condor.pm - log path since 672 only relative?
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Thomas Lisson
> Sent: Thursday, March 31, 2005 4:33 AM
> To: Condor-Users Mail List
> Subject: [Condor-users] Condor.pm - log path since 672 only relative?
> I use the module Condor.pm instead of DagMAN for my huge jobs
> and I have a problem with Condor.pm since 672.
> My submit file looks like this:
> log =
> output = out1
> error = out2
> initialdir =
> In 672, 676 Condor.pm looks for log at
> It doesn't recognize that log is an absolute path.
> If I try log = log, Condor.pm looks for log at
> which also doesn't exist, because it doesn't resolve
> $(Process). So the Condor perl module cannot work.
> Condor.pm versions before 672 work fine, they regognize that
> log is absolute (or they don't look at the initial dir). I
> would like to use the new features from the newer Condor perl
> modules, but how do I tell him to treat log as an absolute path?
Thanks for posting this. You are right in that prior to recently
when we updated this module the Condor.pm module could not monitor
a job which had a log requested relative to Initialdir as it totally
ignored Initialdir. Yet it is still imperative for absolute paths
to work even when Initialdir is being used.
We are adding correct recognition of both Unix and Windows
absolute paths for inclusion in our next releases and I will
post a link to the updated module soon.
Bill ( Condor Team )
> Thomas Lisson
> Condor-users mailing list