10:32:09 AM PDT - Wed, May 30th 2012 |
|
The number of processes created is definitely not something that is easily changed. It's part of the core design of ECCE remote communications. While there is some waste there that could be reduced/streamlined, I think there will always be 3 or 4 processes per job launch. The part that could be streamlined would be related to how ECCE creates a csh shell. That's just because our remote communications logic uses csh syntax going back to the 1990's so a couple days of software development could eliminate that since csh has become much less popular over the years. With a ulimit of 32 on processes though, that's not going to be a guaranteed fix to your problem. Plus, there isn't the funding available to make the required code changes now. As an aside, when ECCE goes open source later this summer then certainly we'd love user contributions to the code base and source code was already released with ECCE 6.3 so someone intent on cleaning up the remote communications could already dive into it. For now though I'll try to help with your other ssh port redirect issue instead.
Gary
|