The Mhash/s reported is the actualized Mhash/s determined by the number of shares passed to the server averaged over the last 7 minutes. The rate you see on your computer is the amount of work your actually doing. I would assume the reason you are seeing 0 is you have a low Mhash/s rate and therefore when you find a share your shares/7 minutes skyrockets but most of the time your shares/7 minutes is 0. This question was answered on the first page of the thread BTW.

HAHA I just copy pasta that to my command line and have been running for days. The port doesn't need to be specified since 8332 is default. The -p switch is already declared if you put your password before "-p 8332" so it doesn't do anything anyway; you can remove -p 8332 in its entirety.

Sounds about right, I'm getting ~8 out of an i7 and it looks like the GTX460 does ~68. https://en.bitcoin.it/wiki/Mining_hardware_comparison. If you're doing graphic related stuff on your computer (games/streaming video) then it'll drop below the numbers on that site.

EDIT: I wrote 64, [Tycho] FTFM

First of all thanks for setting up a second pool for everybody; I recently got into the BTC hype but was having trouble going at it alone. I've been running for about 8 hours with little to no problems, although I don't have much to compare to seeing this is the first pooled experience I have. The only issue I've seen so far is occasionally DiabloMiner will give the following feedback:

85413/90697 khash/secException in thread "DiabloMiner Executor (GeForce GTX 295
(#1)/2)" java.lang.NullPointerException
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState$Ge
tWorkParser.parse(DiabloMiner.java:731)
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState$Ge
tWorkParser.getWork(DiabloMiner.java:636)
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState$Ge
tWorkParser.update(DiabloMiner.java:630)
        at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState.ru
n(DiabloMiner.java:534)
        at java.lang.Thread.run(Unknown Source)

It would seem that the work returned is null and cannot be parsed. It corrects itself after a while, probably by asking for more work until something comes back. Forgive my noobidity if that's an incorrect assumption.