[gb@tx1 gb]$ ulimit -acore file size (blocks, -c) 0data seg size (kbytes, -d) unlimitedfile size (blocks, -f) unlimitedmax locked memory (kbytes, -l) 4max memory size (kbytes, -m) unlimitedopen files (-n) 1024pipe size (512 bytes, -p) 8stack size (kbytes, -s) 10240cpu time (seconds, -t) unlimitedmax user processes (-u) 7168virtual memory (kbytes, -v) unlimited(11:04:49 AM) balfanz: 10 megs stack is the only thing i see that looks limiting in this case(11:06:06 AM) balfanz: perhaps we need to pass by reference instead of value on some procs...(11:10:57 AM) nickd475: this is the same code we've been using for pasha, plus unimark doesnt use all of the brokering stuff that has caused problems in the past that pasha uses(11:11:13 AM) nickd475: it does loop over all loads, and then each vin assined to that load(11:12:00 AM) balfanz: would you agree that stack size is the only possible ulimit we've exceeded?(11:13:03 AM) balfanz: and that we pass by value mostly vs. by ref?(11:13:17 AM) nickd475: im not familar with max locked memory (kbytes, -l) 4, but other than that yes(11:16:33 AM) nickd475: yes we do pass by value mostly, but it is mostly scalars anyway, because this is grabbing info about the load and reformatting it, the returned values from Load::fetchList is an array of loads (i guess this could be an array ref, but it just formats the sql and vars and calls fetchall_hashrefs i believe) and $load->getPayload which returns an array of PayLoad::auto objects