Re: storage
Kenneth Gober <[email protected]> Wed, 29 Jul 2026 08:06:01 -0400
| Newsgroups | gmane.os.openbsd.misc |
|---|---|
| Message-ID | <CANHrbpd3sru8YLBiMj4hgL4sd6uKvnkTLBkFu5CwE0yi4EG_5Q@mail.gmail.com> |
--0000000000003734670657bec817 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jul 28, 2026 at 2:43=E2=80=AFPM Gustavo Rios <[email protected]= m> wrote: > Hi folks! > > I need to share home directory along a set o shell acount servers, i.e., = 4 > servers. I was thinking about using nis and amd. Is amd relevant yet ? Ar= e > there alternatives? > One obvious alternative to using the auto-mount daemon (amd) is to statically mount the home directory filesystems on each server. This entirely avoids all the bother of configuring amd (notably maintaining the mapping file and keeping it synced), and is trivially simple if all your home directories are stored on a single server. If the home directories are distributed among the shell account servers, that's straightforward as well. On server 1 you might have: {DUID1}.h /u1 ffs rw,nodev,nosuid 1 2 server2:/u2 /u2 nfs rw,nodev,nosuid 0 0 server3:/u3 /u3 nfs rw,nodev,nosuid 0 0 ... And on server 2 you might have: server1:/u1 /u1 nfs rw,nodev,nosuid 0 0 {DUID2}.h /u2 ffs rw,nodev,nosuid 1 2 server3:/u3 /u3 nfs rw,nodev,nosuid 0 0 ... And so on. -ken --0000000000003734670657bec817 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><span style=3D"background-color:transpare= nt">On Tue, Jul 28, 2026 at 2:43=E2=80=AFPM Gustavo Rios <<a href=3D"mai= lto:[email protected]">[email protected]</a>> wrote:</span></d= iv><div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gm= ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,= 204,204);padding-left:1ex"><div dir=3D"ltr"><div>Hi=C2=A0folks!<br clear=3D= "all"></div><div><br></div><div>I need to share home directory along a set = o shell acount servers, i.e., 4 servers. I was thinking about using nis and= amd. Is amd relevant yet ? Are there alternatives?</div></div></blockquote= ><div><br></div><div>One obvious alternative to using the auto-mount daemon= (amd) is to statically mount the home directory filesystems on each server= . This entirely avoids all the bother of configuring amd (notably maintaini= ng the mapping file and keeping it synced), and is trivially=C2=A0<span sty= le=3D"background-color:transparent">simple if all your home directories are= stored on a single server.</span></div><div><span style=3D"background-colo= r:transparent"><br></span></div><div><span style=3D"background-color:transp= arent">If the home directories are distributed among the shell account serv= ers, that's straightforward as well. On server 1 you might have:</span>= </div><div>{DUID1}.h /u1 ffs rw,nodev,nosuid 1 2</div><div>server2:/u2 /u2 = nfs rw,nodev,nosuid 0 0</div><div>server3:/u3 /u3 nfs rw,nodev,nosuid 0 0</= div><div>...</div><div><br></div><div>And on server 2 you might have:</div>= <div>server1:/u1 /u1 nfs rw,nodev,nosuid 0 0</div><div>{DUID2}.h /u2 ffs rw= ,nodev,nosuid 1 2</div><div>server3:/u3 /u3 nfs rw,nodev,nosuid 0 0</div><d= iv>...</div><div><br></div><div>And so on.</div><div><br></div><div>-ken</d= iv></div></div> --0000000000003734670657bec817--