On Apr 4, 2012 5:11 PM, "Jaime Frey" <jf...@cs.wisc.edu> wrote:
> I've scanned the changes in Condor 7.7.5 and I also don't see anything > that would explain a change in the memory behavior of jobs. I assume > you're submitting your jobs under the vanilla universe. Yes. > Have you tried logging into the execute nodes and running the programs > interactively? That's a good way to test if something other than Condor > changed and is responsible for the difference. Yes, I did that and the problem is not present. This is what made me blame Condor and file this bug. > You can also try running condor_ssh_to_job while a job is running to get > an interactive session with the same environment as your job. You can > examine the environment variables, etc. for any odd settings. You even > submit a sleep job, then use condor_ssh_to_job to start your program > interactively in the environment Condor sets up, possibly tweaking > environment variables first. I haven't done that yet, and will test this next -- thanks for this suggestion! I will report back if I can replicate the behavior. Thanks, Michael
