RE: [Condor-users] VirtualMemory attribute under Linux 2.6 kernel

["Kewley, J \(John\)" <j.kewley@xxxxxxxx>]

>From memory,
1) Probably, I think you find out quite quickly that things aren't going to
   work out fine.
2) Yes

If you set the values manually in the condor.config[.local] then all will work
OK. 

Again from memory, I think that the 6.7 series (later versions) got that fixed,
I don't know whether it was fixed in 6.6.9 (that would depend on whether it was considered
missing functionality or a bug).

Sorry I can't be more specific, but I am sure what you describe is what I did to setup a
few machines during last year's UK Condor Week.

JK

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx on behalf of Bruce Beckles
Sent: Wed 22/06/2005 17:25
To: Condor-Users Mail List
Subject: [Condor-users] VirtualMemory attribute under Linux 2.6 kernel
 

Hi -

 	I know that under the Linux 2.6 kernel, the Condor 6.6 series will 
set the VirtualMemory and TotalVirtualMemory ClassAd attributes to 0 
(presumably because of the change to the relevant bit of the /proc 
filesystem under 2.6).  I have two questions about this:

1) Does this matter? i.e. does Condor care about this, or will anything
    not work properly because of this?  I assume that if users submit jobs
    which have either of these attributes in their Requirements then those
    jobs won't get matched to machines with the 2.6 kernel (unless the
    Requirement was that the attribute was 0!).

2) Is there any way I can override this setting, say by setting something
    in the condor_config file (like I can do with MEMORY= for the Memory
    ClassAd attribute) or in the Condor daemons' environment?

 	Thanks,

 	  Bruce

--
Bruce Beckles,
e-Science Specialist,
University of Cambridge Computing Service.
_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/condor-users