2.0.a23: cfservd doesn't obey ExpireAfter or IfElapsed

[David Bianco]

I've got the following lines in my cfservd.conf:

        ExpireAfter = 10

        IfElapsed = 0

Since these are test runs, I've purposely set IfElapsed to 0 so I can
run repeatedly without having to wait.

If I run "cfrun -v" for a host, I get the following output from cfrun:

        cfservd Couldn't get a lock -- too soon: IfElapsed 0, ExpireAfter 10

I think this is weird, because with a value of 0 for IfElapsed, it should
never be too soon to run.  At least the values print correctly in this
output, though.  

Now the output of cfservd -v -debug is quite different.  Among many other
lines, I see the following just before the connection closes:

        GetLock(cfd,exec,time=1013531387), ExpireAfter=30, IfElapsed=5
        GetLastLock()
        myhost.jlab.org: Too soon for cfd.exec (4/5 minutes elapsed)

Somehow, the values for ExpireAfter and IfElapsed are being set to 30
and 5, respectively.  I don't even have any other config files with those
values set to those parameters, so I know it's not getting confused by the
wrong input files.  Can anyone else confirm this behavior?

        David

-- 
David J. Bianco, GSEC           <address@hidden>
Thomas Jefferson National Accelerator Facility

     The views expressed herein are soley those of the author and
            not those of SURA/Jefferson Lab or the US DOE.