Re: [Condor-devel] Reserved swap space issue

["Devaraj Das" <ddas@xxxxxxxxxxxxx>]

I found out why the function (sysapi_swap_space) used to return negative
numbers. The variable used to store the kernel-returned swap-space value is
declared as an (signed) int. However, the value stored (4020785152) is so
big that it has to be treated as an 'unsigned int' later.
Yes, I discovered this in the process of freezing the freebsd port.

-----Original Message-----
From: Erik Paulson [mailto:epaulson@xxxxxxxxxxx] 
Sent: Monday, February 20, 2006 11:14 PM
To: Devaraj Das
Cc: condor-devel@xxxxxxxxxxx
Subject: Re: [Condor-devel] Reserved swap space issue

On Mon, Feb 20, 2006 at 06:14:30PM +0530, Devaraj Das wrote:
> Hi,
> Setting RESERVED_SWAP space to zero in the config files doesn't seem to
> affect the condor_shadow processes. Upon investigation, I found that in
the
> file baseshadow.C, checkSwap doesn't do the necessary checks for
> RESERVED_SWAP = 0 (as done, for example, in schedd.C:canSpawnShadow). That
> was causing some jobs to fail since on my platform sysapi_swap_space, for
> some reason, returns a negative number.
> I am using condor-6.7.13. Is this taken care of in the later versions?

No, it hasn't been. It's probably better to fix sysapi so you don't
return a negative number (this is for your FreeBSD port?)  - there may
be other places that Condor uses the swap numbers that you'll eventually 
have to fix anyway.

-Erik