05-12-2009
How to do the Loadbalancing on NIS Server in Solaris 10 sparc
We set-up master/slave servers for NIS on Solaris10 Sparc. We are trying to synchronize them in such a way that if one server is down then other server would pick-up and also do load balancing. We are stuck on this part. Do you have any documentation or point to the documentation where we get some help in understanding how to sync master-slave NIS servers and also set-up for load balancing.
Any help on this is appreciated.
8 More Discussions You Might Find Interesting
1. Solaris
hey. i have been installing the VNC server from the solaris Companion cd under solaris 8 SPARC,
when i try to open the vncserver i get: Xvnc is not in your PATH, how do i add it to the PATH ? and how do i install it if i need to do that,
thx (0 Replies)
Discussion started by: mads-nielsen
0 Replies
2. Solaris
Hi there,
I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server.
*I have re-compiled the linux kernel t support ufs fstype with ro mount support.
filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies
3. UNIX for Dummies Questions & Answers
Hi Gurus
can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?
regards,
Israel. (9 Replies)
Discussion started by: iga3725
9 Replies
4. Red Hat
Hi Friends,
I am setting up my new public DNS server using bind 9 on RHEL5.5 64bit.
I also want to have an another DNS failover server on one of my another datacenter. My question is, if i installed an new slave DNS server on the second datacenter and configure the zone transfer, do it will be... (2 Replies)
Discussion started by: arumon
2 Replies
5. Solaris
Hi,
I am getting following service error on one of the sparc servers running solaris 10 -
Code :
$ svcs -a | grep "maintenance"
maintenance Nov_08 svc:/application/management/sma:default
$ svcs -xv
svc:/application/management/sma:default (net-snmp SNMP daemon)
State: maintenance... (8 Replies)
Discussion started by: sunadmin
8 Replies
6. Solaris
Hello all, thanks for reading my question:
So I've been a Unix/Linux SysAdmin for a couple years, and I'm a bit over my head running solo, trying to set up LDoms using Oracle VM Server 3.1 for SPARC. I've been very careful, and things have gone well up until the point I try to access the new... (9 Replies)
Discussion started by: Lyxix
9 Replies
7. UNIX for Advanced & Expert Users
Hi,
I hope somebody can help me. I wand to Move my NIS server on Solaris 10
(there are 2 Slaves on Linux) to CentOS7.
Do you have any procedures or experience to do this?
Thanking in anticipation! (2 Replies)
Discussion started by: Penguin99
2 Replies
8. Solaris
Based on the NIS migration tests I did and another question I posted earlier on.
https://www.unix.com/solaris/272021-solaris-8-md5-encryption-support.html
I tried to downgrade NIS linux encryption to DES to support solaris connection.
So I modified /etc/pam.d/system-auth as below,
password... (0 Replies)
Discussion started by: bestard
0 Replies
LEARN ABOUT FREEBSD
rpc.ypxfrd
RPC.YPXFRD(8) BSD System Manager's Manual RPC.YPXFRD(8)
NAME
rpc.ypxfrd -- NIS map transfer server
SYNOPSIS
rpc.ypxfrd [-p path]
DESCRIPTION
The rpc.ypxfrd utility is used to speed up the distribution of very large NIS maps from NIS master to NIS slave servers. The normal method
for transferring maps involves several steps:
o The master server calls yppush(8) to inform the slave servers to start a transfer.
o The slave servers invoke ypxfr(8), which reads the entire contents of a map from the master server using the yp_all() function.
o The ypxfr(8) program then creates a new map database file by using the db(3) library hash method to store the data that it receives
from the server.
o When all the data has been retrieved, ypxfr(8) moves the new file into place and sends ypserv(8) on the local machine a
YPPROC_CLEAR to tell it to refresh its database handles.
This process can take several minutes when there are very large maps involved. For example: a passwd database with several tens of thousands
of entries can consume several megabytes of disk space, and it can take the db(3) library package a long time to sort and store all the
records in a hash database. Consider also that there are two sets of map files: master.passwd.by{name,uid} and passwd.by{name,uid}.
The rpc.ypxfrd utility speeds up the transfer process by allowing NIS slave servers to simply copy the master server's map files rather than
building their own from scratch. Simply put, rpc.ypxfrd implements an RPC-based file transfer protocol. Transferring even a multi-megabyte
file in this fashion takes only a few seconds compared to the several minutes it would take even a reasonably fast slave server to build a
new map from scratch.
The rpc.ypxfrd utility uses the same access restriction mechanism as ypserv(8). This means that slave servers will only be permitted to
transfer files if the rules in the securenets database permit it (see ypserv(8) for more information on securenets). Furthermore, only slave
servers using reserved ports will be allowed to transfer the master.passwd maps.
OPTIONS
The following option is available:
-p path
This option can be used to override the default path to the location of the NIS map databases. The compiled-in default path is
/var/yp.
FILES
/var/yp/[domainname]/[maps] The NIS maps for a particular NIS domain.
SEE ALSO
yp(8), yppush(8), ypserv(8), ypxfr(8)
AUTHORS
Bill Paul <wpaul@ctr.columbia.edu>
BUGS
The FreeBSD ypxfrd protocol is not compatible with that used by SunOS. This is unfortunate but unavoidable: Sun's protocol is not freely
available, and even if it were it would probably not be useful since the SunOS NIS v2 implementation uses the original ndbm package for its
map databases whereas the FreeBSD implementation uses Berkeley DB. These two packages use vastly different file formats. Furthermore, ndbm
is byte-order sensitive and not very smart about it, meaning that am ndbm database created on a big endian system cannot be read on a little
endian system.
BSD
June 2, 1996 BSD