10-21-2008
Thanks for the replies. Can you suggest me what will be the most suitable option for my case? What I need is that I need to write directly to remote location. Number of files would be fairly large ranging around some thousands. But file size is small. It needs to be secure(of course), open standard, supported on our plaforms and easily available. The host that will be written directly runs Solaris 8 and the writting host runs HP-UX 11i.
Thanks again for your suggestions.
Stephen W.
7 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone.
I have 3 machines, let's call them store, node1 and node2.
I have to mount on node1 and node2 the same directory of store.
So, I launch the sshfs command on node1 and everything works fine.
But when I try to do that on node2, it hangs for a while and then I... (0 Replies)
Discussion started by: canduc17
0 Replies
3. Shell Programming and Scripting
Hi everyone.
I have 3 machines, let's call them store, node1 and node2.
I have to mount on node1 and node2 the same directory of store.
So, I launch the sshfs command on node1 and everything works fine.
But when I try to do that on node2, it hangs for a while and then I obtain:... (0 Replies)
Discussion started by: canduc17
0 Replies
4. Solaris
I have an automated testing script that relies on the dev box being able to see production's (NFS) share. It uses rsync and ssh to handle transfers and command execution; however, it also needs the production share mounted in order to run Perl code against it when Unix commands via ssh will not do.... (2 Replies)
Discussion started by: effigy
2 Replies
5. Shell Programming and Scripting
Hello all,
First time posting, although the site has helped solve many problems in the past!
I would like to create a script to simplify a series of commands that I run:
Log into the ssh-server (RSA key)
ssh username@hostname -p 6110
Once there, I mount a truecrypt volume:
truecrypt... (3 Replies)
Discussion started by: freshtoast
3 Replies
6. Shell Programming and Scripting
Hi, I am new to this forum.
I want to setup my personal Dropbox between my home server and the work station in the office.
I followed this tutorial
danbishop.org/2011/09/10/...-in-os-x-lion/and it works great. :)
The trouble now is I am not sure how I can make it to start on boot.
... (3 Replies)
Discussion started by: macpc
3 Replies
7. UNIX for Dummies Questions & Answers
I'm trying to setup a link between my home pc (work-machine) and a server at work (tar-machine) that is behind a gateway (hop-machine) and not directly accessible.
my actions:
work-machine$ ssh -L 1234:tar-machine:22 hop-machine
work-machine$ ssh -p 1234 user@127.0.0.1
- shh access on... (1 Reply)
Discussion started by: Vathau
1 Replies
XON(1) General Commands Manual XON(1)
NAME
xon - start an X program on a remote machine
SYNOPSIS
xon remote-host [-access] [-debug] [-name window-name] [-nols] [-screen screen-no] [-user user-name] [command ...]
DESCRIPTION
Xon runs the specified command (default xterm -ls) on the remote machine using rsh, remsh, or rcmd. Xon passes the DISPLAY, XAUTHORITY and
XUSERFILESEARCHPATH environment variables to the remote command.
When no command is specified, xon runs 'xterm -ls'. It additionally specifies the application name to be 'xterm-remote-host' and the win-
dow title to be '-fIremote-host'.
Xon can only work when the remote host will allow you to log in without a password, by having an entry in the .rhosts file permitting
access.
OPTIONS
Note that the options follow the remote host name (as they do with rlogin).
-access
Runs xhost locally to add the remote host to the host access list in the X server. This won't work unless xhost is given permission
to modify the access list.
-debug Normally, xon disconnects the remote process from stdin, stdout and stderr to eliminate the daemon processes which usually connect
them across the network. Specifying the -debug option leaves them connected so that error messages from the remote execution are
sent back to the originating host.
-name window-name
This specifies a different application name and window title for the default command (xterm).
-nols Normally xon passes the -ls option to the remote xterm; this option suspends that behaviour.
-screen screen-no
This changes the screen number of the DISPLAY variable passed to the remote command.
-user user-name
By default, xon simply uses rsh/remsh/rcmd to connect to the remote machine using the same user name as on the local machine. This
option cause xon to specify an alternative user name. This will not work unless you have authorization to access the remote
account, by placing an appropriate entry in the remote users .rhosts file.
BUGS
Xon can get easily confused when the remote-host, user-name or various environment variable values contain white space.
Xon has no way to send the appropriate X authorization information to the remote host.
X Version 11 Release 6.6 XON(1)