Sponsored Content
Top Forums Shell Programming and Scripting Solaris 9 Home Directory, Two Machines Sharing a NAS Post 303023994 by jim mcnamara on Wednesday 26th of September 2018 09:57:27 PM
Old 09-26-2018
Clarification:

We have two boxes. Box 1 is parent. Box 1 owns the filesystem. Box1 shares the filesystem via NFS or samba or whatever. Box 1 does not care who connects to the filesystem and then remote mounts it - via NFS. So you really have a proxy acting in box 1 in its very own kernel space when a request comes over the network. Box 1 controls entirely the NFS mounted disk, because it is actually physically mounted on box 1, not box 2.

Box 2 now runs an NFS/Samba client that connects over to box 1 via the smb protocol (example protocol). Box 2 has a symlink to the NFS mountpoint (that lives on box 2) then points to box 1. This is a mountpoint that connects as a proxy to the real disk on box 1.

This works great. I do not know what Made In Germany saw in your post, but what I described, I think, is clear. Samba or NFS works fine on Solaris 9. You will need to read a little on configuring your fileserver on Box 1. You do not seem to be running NFS to make box 1 a fileserver, and make box 2 a client of that fileserver.

The only weenie you need to know:
As of 2013 the NFS version on Solaris 9 has/had a bug.

Before rebooting:
If you have a user that stays logged on in spite of policy (I did), then you must kill all users processes on both systems. And any process that has the filesystem in question open. All logged on users and possibly system maintenance processes can have open files/directories there.

Why? If there is a file held open on box 2 (i.e., some user has a process with the current directory aimed "in" the NFS mount) then box 1 will hang on shutdown. Forever. If you force kill box 1, it will not rebuild NFS , so you lose the connection when you do reboot . Forever. Forever = you have to destroy and rebuild the connection on both sides. And it fails sometimes. As of 2015 there was a patch for this on Solaris 10, Solaris 11 did not have the problem, and no patch for Solaris 9. Verify this with Oracle support, if you still have support for your Solaris 9 box.

See: Solaris Operating System - Releases
This User Gave Thanks to jim mcnamara For This Post:
 

7 More Discussions You Might Find Interesting

1. HP-UX

sharing a directory

Im trying to simply share a directory on one unix server and mount that share on a different unix server. There is no "share" command like on sun. What is the command to create a share on HP-UX? (2 Replies)
Discussion started by: bski
2 Replies

2. IP Networking

Printer Sharing on a Mixed(Windows/Linux) Home Network

Sometimes you get the tiger...but sometimes he get you and this latest home network “project” of mine has gnawed on me pretty badly. Perhaps you can offer some technical help. It will be heartily appreciated. I have a small home network initially comprising two computers running Windows... (1 Reply)
Discussion started by: Annatar
1 Replies

3. UNIX for Advanced & Expert Users

Mounting NAS Drive on solaris

Hi, Im running 32-bit solaris on sparc. We have a NAS(Network attached drive), with its IP address, username and password. I'd like to be able to mount it on the solaris machine, and unmount it. The best possibility would be able to mount it simulataneously on 2 or more systems. Please... (9 Replies)
Discussion started by: 0ktalmagik
9 Replies

4. Solaris

NISuser home directory movement in Solaris

How to move home directory of NIS user from one system to another system in Solaris. Thanks & Regards Durgaprasad (1 Reply)
Discussion started by: durgaprasadr13
1 Replies

5. UNIX for Dummies Questions & Answers

ssh autologin issue when both machines are having same ~home directory

Hi, I have two machines. M1 and M2 and having a generic id catadm, these two machines having common mount of /u/catadm directory. with this setup, ssh autologin is failing for me and asking me to enter password when i try autologin using this generc id from M1 to M2 catadm-M1$ ssh... (3 Replies)
Discussion started by: rbalaj16
3 Replies

6. Solaris

Sharing a local disk between to solaris machines

Hi, I recently added a disk on a solaris 9 and I wanted to make it accessible for another machine, using the same name here is what i did : On the machine holding the internal disk in vfstab i added the line /dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /SHARED2 ufs 2 yes ... (2 Replies)
Discussion started by: zionassedo
2 Replies

7. Solaris

NFS with a NAS: permanently inconsistent directory state across clients

Hi, I am having some NFS directory consistency problems with the below setup on a local (192.) network: 1. Different permissions (chmod) for the same NFS dir are reflected on different clients. 2. (more serious) an NFS dir created on client1 cannot be accessed on client2; this applies to some... (10 Replies)
Discussion started by: cosmojetz
10 Replies
Box(3I) 						    InterViews Reference Manual 						   Box(3I)

NAME
Box, HBox, VBox - tile interactors in a box SYNOPSIS
#include <InterViews/box.h> DESCRIPTION
A box is a scene of interactors that are tiled side-by-side in the available space. Interactors are placed left-to-right in a horizontal box, and top-to-bottom in a vertical box. A box will try to stretch or shrink the interactors inside it to fit the available space. The natural size of a box is the sum of its ele- ments along the major axis, and the maximum along its minor axis. A box's stretchability (shrinkability) is the sum of its elements along its major axis and the minimum of its elements along its minor axis. PUBLIC OPERATIONS
HBox(...) VBox(...) Create a new box. Zero to seven interactors may be passed as arguments; the interactors are inserted into the box. void Align(Alignment) Set the alignment mode that the box uses to place elements along the minor axis. The default alignment for an hbox is Bottom; other choices are Top and Center. The default alignment for a vbox is Left; other choices are Right and Center. void Insert(Interactor*) Append an interactor to the box. Components of an hbox (vbox) will appear left-to-right (top-to-bottom) in the order in which they are inserted. void Change(Interactor*) Notify the box that the given interactor's shape has changed. If change propagation is true, the box will modify its own shape to reflect the change and notify its parent. Regardless of propagation, the box will recompute the positions of the component interac- tors and update any that have changed. void Remove(Interactor*) Take an element of out a box. Remove does not cause any immediate change to the other components in the box; the Change operation must be called after one or more Removes to update the component positions. SEE ALSO
Glue(3I), Interactor(3I), Scene(3I), Shape(3I) InterViews 15 June 1987 Box(3I)
All times are GMT -4. The time now is 12:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy