moxi listening on wrong port, not working

Moxi seems to not be working - up on 10.1.3.76:51824 (versus 11211)

(4:53:30 PM) ingenthr@gmail.com: # ./memcachetest -h 10.1.3.76:51824
Get operations:
#of ops. min max avg max90th max95th
6740 0 ns 5561 us 170 us 188 us 195 us

Average with 1 threads:
Avg set: 182 us (3260) min: 144 us (0) max: 7993 us (0)
Avg get: 170 us (6740) min: 108 us (0) max: 5561 us (0)
Usr: 0.110983
Sys: 0.447931
Tot: 3.525917
Server time:
Usr: 0.000000
Sys: 0.000000

(4:54:01 PM) jamesmalcolmphillips@gmail.com/72B3B2FF: hmmm
(4:54:04 PM) jamesmalcolmphillips@gmail.com/72B3B2FF: worked for me this time
(4:54:07 PM) jamesmalcolmphillips@gmail.com/72B3B2FF: that's good
(4:54:20 PM) ingenthr@gmail.com: though I'm afraid the data's just going straight into moxi
(4:54:23 PM) ingenthr@gmail.com: based on how the run looks
(4:54:26 PM) jamesmalcolmphillips@gmail.com/72B3B2FF: was using -host not -h
(4:54:30 PM) ingenthr@gmail.com: ah
(4:54:37 PM) ingenthr@gmail.com: yeah, i need to make the argument handling better
(4:54:49 PM) ingenthr@gmail.com: low priority
(4:54:52 PM) jamesmalcolmphillips@gmail.com/72B3B2FF: yup
(4:55:08 PM) ingenthr@gmail.com: so, I don't think this node is working
(4:55:21 PM) jamesmalcolmphillips@gmail.com/72B3B2FF: is Eric's test around somewhere that actually puts stuff in and make sure it comes back out?