Hi Thomas,
> For one thing, you're using just "du" to call the binary, so we can't
> be sure you're calling the same "du" in each case. So, when logged in
> on the remote machine, do "which du" and use the resulting fully
> qualified path in your rexec call.
Check, this is ok - locally an remotel
HACKER Nora asked:
> Unfortunately, this does not explain the difference between the local
> du and the one via rexec on a remote machine. Any help appreciated.
When you're getting different results then you're doing something differently
;-)
For one thing, you're using just "du" to call the bi
