09-07-2011
6,384,
2,214
Join Date: May 2005
Last Activity: 28 October 2019, 4:59 PM EDT
Location: In the leftmost byte of /dev/kmem
Posts: 6,384
Thanks Given: 143
Thanked 2,214 Times in 1,548 Posts
You have several options:
1) NFS
You have to start the NFS subsystem first if it is not already started. Then create an exported directory (you might want to make this a separate file system) on one of the two machines and mount this on the other. Files in there can be accessed by both systems. You seem to be not all too knowledgeabe about systems administration (no offense, but you come across like this), so you best do it via SMIT, which is menu driven all the way.
Advantage: true file sharing and easy to implement (~5 min).
Disadvantage: NFS can effectively hang a system if the network connection breaks and NFS has some really ong timeouts, which is why it is usually not used in production environments as a permanent solution. Some problems with NFS can only be solved by a reboot.
2) FTP (or some securified variant of it)
You just have to start the FTP (or SFTP) subsystem if it is not already started. FTP is not file sharing but file transfer. You copy files from one system to another in order to synchronize its contents. You might want to automate this process and put it in crontab.
Advantage: very reliable and stable. Even if the network breaks for a while there is nothing to do to clean up. No setup at all (for FTP itself).
Disadvantage: FTP is a bit clumsy and you may need to do some scripting to implement this effectively - depending on what exactly you need and what your environment looks like this can range from very little effort to a full-bown project. Another disadvantage is that FTP transfers passwords over the network in clear text, so they could be sniffed. This is why SFTP (Securified FTP) is recommended instead most of the times.
3) RCP or its securified variant SCP or rsync
This is similar to FTP but with a much more "intelligent" client. You will probably need less scripting to implement this effectively. Again, the securified variant SCP is under most circumstances preferable. rsync as well as scp are using ssh as authentication mechanism.
I hope this helps.
bakunin