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

Re: [Condor-users] STARTER_LOCAL_LOGGING for Vanilla Universe?



On Tue, 26 Apr 2005, Erik Paulson wrote:

<snip>
Can someone tell me whether this feature is supported in the Vanilla
universe?  If not, for which universes is it supported?


It's only supported in (it looks like) the standard universe and probably the PVM universe.

<snip>
With condor_fetchlog, you don't really need it anymore.

I disagree. condor_fetchlog only works if the machine the job ran on is (a) still in the pool, (b) hasn't already rotated the relevant log file, and (c) the issuer of the condor_fetchlog command has the administrator level of access for the machine on which the log file resides.


In our setup, machines frequently join and leave the pool, so (a) will often not be true. Obviously (b) is a function of (in part) how many jobs you are running - when our pool goes into production mode we expect this to be 1000s, so (b) is likely to be true only for a very short time after the job has been run. And (c) will NEVER be true for ordinary users.

One of the principal advantages of "remote starter logging" as currently implemented (for those Universes where it is implemented) is that it means users are guaranteed to see the starter log for their job, and they can do so WITHOUT needing either the administrator level of access for the machine on which their job ran *or* having to harass the pool administrator every time they need to see the starter log for a job.

So I do not think that condor_fetchlog can be considered a viable replacement or alternative for the "remote starter logging" feature. As currently implemented, they serve different functions and one is not a replacement or alternative for the other.

(So my implicit question now is: how hard would it be to implement "remote
 starter logging" for other Universes?  Could/would this be considered as
 a possible feature for a future release?)

	-- Bruce

--
Bruce Beckles,
e-Science Specialist,
University of Cambridge Computing Service.