It seems that RM client programs (basicly, just momctl), aren't cleaning
up their local priv ports when TORQUE is built with --disable-rpp.
Try to use momctl a 1000 times and it will start failing when
you run out of priv ports:
$ for a in `seq 1 1000`;do momctl -d 0 -h hpcjr0004 >/dev/null;done
cannot connect to MOM on node 'hpcjr0004', errno=99 (Cannot assign requested address)
cannot connect to MOM on node 'hpcjr0004', errno=99 (Cannot assign requested address)
cannot connect to MOM on node 'hpcjr0004', errno=99 (Cannot assign requested address)
This works fine when using RPP. Can anyone else duplicate this?
--
Garrick Staples, Linux/HPCC Administrator
University of Southern California
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20051208/3724fc54/attachment.bin