SSH works but I'm confused

[Michael Jay_2]

I've configured ssh (on SIM 4.1) and even successfully changed the tools to use our renamed administrator account. I thought all was fine. I created a simple custom command to run the resource kit's uptime utility against the selected servers. This runs fine for all users I've configured to use ssh.

I then created a custom command that basically just nicely formats the uptime output by using a couple UNIX for DOS utilities (expand and sort). This works fine when I run it under my login but when run under any other user it runs uptime.exe fine but errors out when the script attempts to use the expand and sort utilities.

The message returned when run under any use but me is:

The system cannot execute the specified program
(it lists this error for both the sort and expand)

I'm confused as to why it works fine for me and no one else. I've checked Windows Perms and UNIX perms on scripts and user's .ssh files and I've seen nothing different between these other users and myself!

Help! I need to understand what is going on.

TIA.

MJ

[Michael Jay_2]

Forgot to mention that when I try and run the two commands that are failing by doing ssh at the command line (under my account as well as others) the command fails with above mentioned error message.

So SIM is doing something special or different that allows the commands to work at least under my account.

MJ

[Michael Jay_2]

Figured out a bit more this morning. I rebooted the SIM server and logged into SIM with a different account and the script ran fine. I then logged into SIM with a different account and ran the script and it failed as described above.

I then restarted the OpenSSH service and the first user to run the script it works fine for but any user after that fails.

So, I would say this is a bug in the OpenSSH software. I'm using the default that came with SIM 4.1. Is there possibly a newer version that I could upgrade to?

Thanks.

MJ

[Rich Purvis]

Michael,
I am not an SSH expert but there is a new version with specific SSH fixes, it is described in this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=860682

Perhaps this will work better for you,

-Rich