Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to find out which server is LDAP/NIS master? Post 302984113 by Scrutinizer on Thursday 20th of October 2016 06:54:54 PM
Old 10-20-2016
What OS are you using?
And what LDAP client does the system use?

You could just look at the configuration file, to know which servers the LDAP client uses. If the LDAP client software is configured to perform a permanent bind you could also look at netstat to see which servers are being communicated with on ports 389/tcp and 636/tcp.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ldap replacement NIS

Hi, I am a solaris administrator who is currently working in a solaris 2.6,7,8,9 environment. We are using NIS for centralised account authentication, groups, host name resolution and most importantly automounting. NIS , over the last few months has been rearing its notorious ugly head, and to be... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

2. UNIX for Advanced & Expert Users

SUSE 9 and 10 NIS clients with RedHat 8.0 NIS server not working

We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave. We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation. However, no matter what i do, the SUSE machines will not talk to the NIS Servers. If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies

3. UNIX for Advanced & Expert Users

NIS master / slave problems

Our NIS master server went down. We have since fixed it and brought it back up. However all of are machines still point to the slave server when looking at it with ypwhich. My question is how do i point the servers back to the master. Frank (2 Replies)
Discussion started by: frankkahle
2 Replies

4. UNIX for Advanced & Expert Users

Moving NIS master to new machine

I am running a DNS/NIS server on and older 2.6 system. I would like to move it to a newer system running Sol9. I have not found a good HOWTO and was looking for some advice. Thanks in advance. Dave (4 Replies)
Discussion started by: dlalonde
4 Replies

5. UNIX for Advanced & Expert Users

NIS+ to LDAP

After months of threats, we're finally migrating servers from NIS+ to LDAP. :eek: I'm happy using niscat, nisgrep etc and now it seems I have to use ldapsearch which is far from being a simple CLI! Are there any easy (easier?) ways to interrogate the LDAP directory? :confused: Jerry (2 Replies)
Discussion started by: JerryHone
2 Replies

6. Solaris

Problem while setting NIS master on Solaris 10

Hi All, I get below error while running cd /var/yp /usr/sbin/ypinit -m Error Code - 1 updated netmasks make : warning : target all not remade because of errors current working dir /var/yp *** error code 1 *** make : fatal error : command failed for target 'k' error running... (4 Replies)
Discussion started by: naw_deepak
4 Replies

7. Solaris

Error while configuring NIS master

Hello - I have a Solaris machine, which I would like to configure as NIS master. When I run the command /usr/sbin/ypinit -m, I see below output. I am enclosing them in tags. /usr/sbin/ypinit -m In order for NIS to operate sucessfully, we have to construct a list of the NIS servers. Please... (1 Reply)
Discussion started by: manju--
1 Replies

8. HP-UX

NIS Master and Client problem

I have a NIS Master server and NIS Clients. But when I started the service all the process and files that should be owne by root apper by the owner 0 This is an example 0 1709 1708 0 10:06:10 ? 0:00 /usr/sbin/nfsd 4 0 1710 1709 0 10:06:10 ? 0:00 /usr/sbin/nfsd 4 0 1708 1 0 10:06:10 ? 0:00... (2 Replies)
Discussion started by: GCSG
2 Replies

9. Red Hat

Yppasswdd not running on nis master server

Goodmorning i am preparing Nis for my test lab.Running Redhat 5.4 on master and centos for my client.Master server running portmap,ypserv,yppasswdd and client running portmap,ypbind and ypxfrd. ypcat and other yp commands are running fine frm client.But when i try yppasswdd on client to change... (1 Reply)
Discussion started by: Vaibhav.T
1 Replies

10. UNIX Desktop Questions & Answers

How can I replicate master master and master master MySQL databse replication and HA?

I have an application desigend in PHP and MySQl running on apache web server that I is running on a Amazon EC2 server Centos. I want to implement the master-master and master slave replication and high availability disaster recovery on this application database. For this I have created two... (0 Replies)
Discussion started by: Palak Sharma
0 Replies
SLAPD(8C)																 SLAPD(8C)

NAME
slapd - Stand-alone LDAP Daemon SYNOPSIS
/usr/sbin/slapd [-f slapd-config-file] [-h URLs] [-d debug-level] [-n service-name] [-s syslog-level] [-l syslog-local-user] [-r directory] [-u user] [-g group] DESCRIPTION
Slapd is the stand-alone LDAP daemon. It listens for LDAP connections on any number of ports (default 389), responding to the LDAP opera- tions it receives over these connections. slapd is typically invoked at boot time, usually out of /etc/rc.local. Upon startup, slapd nor- mally forks and disassociates itself from the invoking tty. If configured in /etc/openldap/slapd.conf, the slapd process will print its process ID ( see getpid(2) ) to a .pid file, as well as the command line options during invocation to an .args file ( see slapd.conf(5) ). If the -d flag is given, even with a zero argument, slapd will not fork and disassociate from the invoking tty. Slapd can be configured to provide replicated service for a database with the help of slurpd, the standalone LDAP update replication dae- mon. See slurpd(8) for details. See the "OpenLDAP Administrator's Guide" for more details on slapd. OPTIONS
-d debug-level Turn on debugging as defined by debug-level. If this option is specified, even with a zero argument, slapd will not fork or disas- sociate from the invoking terminal. Some general operation and status messages are printed for any value of debug-level. debug-level is taken as a bit string, with each bit corresponding to a different kind of debugging information. See <ldap.h> for details. -s syslog-level This option tells slapd at what level debugging statements should be logged to the syslog(8) facility. -n service-name Specifies the service name for logging and other purposes. Defaults to basename of argv[0], i.e.: "slapd". -l syslog-local-user Selects the local user of the syslog(8) facility. Values can be LOCAL0, LOCAL1, and so on, up to LOCAL7. The default is LOCAL4. However, this option is only permitted on systems that support local users with the syslog(8) facility. -f slapd-config-file Specifies the slapd configuration file. The default is /etc/openldap/slapd.conf. -h URLlist slapd will serve ldap:/// (LDAP over TCP on all interfaces on default LDAP port). That is, it will bind to using INADDR_ANY and port 389. The -h option may be used to specify LDAP (and LDAPS) URLs to serve. For example, if slapd is given -h ldap://127.0.0.1:9009/ ldaps:/// ldapi:/// , It will bind 127.0.0.1:9009 for LDAP, 0.0.0.0:636 for LDAP over TLS, and LDAP over IPC (Unix domain sockets). Host 0.0.0.0 represents INADDR_ANY. A space separated list of URLs is expected. The URLs should be of LDAP (ldap://) or LDAP over TLS (ldaps://) or LDAP over IPC (ldapi://) scheme without a DN or other optional parameters. Support for the latter two schemes depends on selected configuration options. Hosts may be specified by name or IPv4 and IPv6 address formats. Ports, if specfied, must be numeric. The default ldap:// port is 389 and the default ldaps:// port is 636. -r directory Specifies a chroot "jail" directory. slapd will chdir(2) then chroot(2) to this directory after opening listeners but before any reading any configuration file or initializing any backend. -u user slapd will run slapd with the specified user name or id, and that user's supplementary group access list as set with initgroups(3). The group ID is also changed to this user's gid, unless the -g option is used to override. -g group slapd will run with the specified group name or id. Note that on some systems, running as a non-privileged user will prevent passwd back-ends from accessing the encrypted passwords. Note also that any shell back-ends will run as the specified non-privileged user. EXAMPLES
To start slapd and have it fork and detach from the terminal and start serving the LDAP databases defined in the default config file, just type: /usr/sbin/slapd To start slapd with an alternate configuration file, and turn on voluminous debugging which will be printed on standard error, type: /usr/sbin/slapd -f /etc/openldap/slapd.conf -d 255 SEE ALSO
ldap(3), slapd.conf(5), slurpd(8) "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/) BUGS
See http://www.openldap.org/its/ ACKNOWLEDGEMENTS
OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan LDAP 3.3 Release. OpenLDAP 2.0.27-Release 5 Novemeber 2000 SLAPD(8C)
All times are GMT -4. The time now is 09:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy