Remote shell

[Luca Frigatti]

Hi all,
does anybody know an alternative to remote shell to execute procedure from a Windows client on a HP-UX server?

Thanks in advance for your help and your support.

Luca

[Stefan Farrelly]

The HP-UX server is not going to allow you to run a procedure from a remote client with some sort of authentication, which means you either have to write a C program which runs on your PC which talks to a C program running as a deamon on your HP-UX server to do a task - but this is difficult to setup.

To do it the easy way you need to use;

remsh, rsh, rexec (remote shell)
ssh, ssh2 (secure remote shell)

It is possible to write a script to use telnet (with the appropriate waits to allow an automatic userid+password to be passed in a script) but this will take some script writing. You can search the itrc forums for how to do this.

Or you could use something like ftp to the HP-UX server then upload a script to a directory where a cron job which is already running will pick it up and run it.

[A. Clay Stephenson]

One method would be to setup a Perl server on your HP box that communicates with a Perl client on your Windows box via sockets. It's not trivially easy but it's not terribly difficult either. You can get a free version of Perl to run on your Windows box.

[Tim D Fulford]

As above...

What do you want to do though? maybe PC-NFS would fit the bill or simple ftp. - just some ideas if they help great

Tim

[Frank Slootweg]

As Tim mentioned, please explain what you want to do, and please explain why you can not use r[em]sh.

[Tim D Fulford]

No expert time, I thought samba did something like this.... I could easily be wrong.... take a look

http://us1.samba.org/samba/samba.html

Tim

[Mark Greene_1]

If the procedures are scheduled and not an "on demand" situation, use cron instead.

If the procedures are the same but needed on-demand, fire-up apache and connect via a browser to a webpage that does some authentication and then allows for a script to be run (and auto-disconnects if the authentication fails).

Or, create a user ID that exec's a script that has a menu to run the procedures that you need, and trap all the usual signals. This way anyone logging in cannot get the commandline, and if they try and break out of the script, they lose the connection. Then you can just use window's telnet program for access.

HTH
Mark

[Dave La Mar]

Luca -
We perform this very function using the "exec site" command in
ftp jobs coming from our IBM mainframe.
In using this we execute scripts that are resident on the remote machine, much like remsh does.
No preference here ....
We use site exec in mainframe to unix or NT and remsh in unix to unix.

Best of luck.
dl