Re: Environment Settings

On Tue, Jul 10, 2007 at 11:29:40AM -0600, Jialing Liang wrote:
Thanks for the detailed reply. My problem is the $HOME is shared:
If I want to have "barney=rubble" for host1 and "barney=block" for
host2, and the $HOME/.ssh/environment and $HOME/.kshrc are shared
between host1 and host2, so I am facing what to put.

1) Set "PermitUserEnvironment yes" in sshd_config.
2) Put "ENV=$HOME/.kshrc" in ~/.ssh/environment on the server.
3) Put your public key in ~/.ssh/authorized_keys on the server.
4) In ~/.kshrc on the server, put:

case $(hostname) in
host1) barney=rubble;;
host2) barney=block;;
esac

Now we're back to what I said in the very first reply I made in this
thread.

Relevant Pages

  • Re: remote inter-program communication?
    ... > the server on host1 to find out. ... When host1 starts loading, ... > application on host2 doesn't need to change. ...
    (comp.unix.admin)
  • Re: Volume Manager information not persistent across reboots
    ... metaset output is not same on the two nodes. ... On host1: Multi-owner is NOT recognised, Master is recognised, host2 is ... Host Owner Member ...
    (comp.unix.solaris)
  • isakmpd/ipsec, routing, Host-to-Site
    ... Host1 will be a gateway and has a ... the external network and gets its IP-Address, default route, DNS etc. ... I configured isakmpd on Host2 to contact Host1, ...
    (comp.unix.bsd.openbsd.misc)
  • Re: How to open an application in a remote x session
    ... will opne up on the xdisplay the user has running on host1. ... To do what the OP wants requires trust between the user on host1 and the user on host2. ... Security is important in this issue, otherwise a user on host2 could log into host1 and capture all the key presses of the user on host1 (X controls the keyboard as well as the display, if you provide access to the X server you potentially allow a user to intercept all keypress events). ... They can do that by issuing "xhost localhost" or "xhost hostname" where hostname is host1's hostname. ...
    (Fedora)
  • Re: Process on one host cannot see (in time) file just created by another process on another host
    ... host1 would first create a file called host1.txt and host2 would create ... They would then read from a text file that lists all the hosts running ... You need to FLUSH the writes and file creations to the disk...otherwise the actual files are still held in buffers and do not exist on the disk as such. ...
    (comp.os.linux.misc)