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

Re: [Condor-users] Mixed 32-bit and 64-bit Linux Pool

Condor will give your job machines with the same architecture and operating
system version as the machine running condor_submit. In another words, condor
append next expression to your requirements.
( TARGET.Arch == "X86_64" ) && ( TARGET.OpSys == "LINUX" )

If you want use both 32-bit and 64-bit machines you can set next requirements
Requirements = (Arch == "INTEL" && OpSys == "LINUX") || \
               (Arch == "X86_64" && OpSys =="LINUX")

You have to also prepare both 32 and 64 bit version of executable. Compiler gcc
have flags for this purpose -m32 and -m64

gcc -O2 -m32 -o example.INTEL example.c
gcc -O2 -m64 -o example.X86_64 example.c

And last change in your submit description file will be.
Executable   = example.$$(OpSys)

Details in manual:


On Wed, Nov 30, 2011 at 01:51:50PM -0500, Rich Pieri wrote:
> I am soon going to be upgrading about 2/3 of my Condor pool from 32-bit SL5 to 64-bit SL5.  The remaining 1/3 or so have 32-bit CPUs so they they're stuck.  Are there any gotchas should my users and I be aware of?  Obviously, 64-bit code won't run on the older hardware, but condor_submit's default behavior should make that a non-issue.
> Thanks.
> -- 
> Rich Pieri <ratinox@xxxxxxx>
> MIT Laboratory for Nuclear Science
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/