Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 172 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

slapd.replog



SYNOPSIS

       slapd.replog slapd.replog.lock


DESCRIPTION

       The  file slapd.replog is produced by the stand-alone LDAP
       daemon, slapd(8), when  changes  are  made  to  its  local
       database  that are to be propagated to one or more replica
       slapds.  The file consists of zero or more  records,  each
       one  corresponding to a change, addition, or deletion from
       the slapd database.  The file is meant to be read and pro­
       cessed  by slurpd(8), the stand-alone LDAP update replica­
       tion daemon.  The records are separated by a  blank  line.
       Each record has the following format.

       The  record  begins  with one or more lines indicating the
       replicas to which the change is to be propagated:

            replica: <hostname[:portnumber]>

       Next, the time the change took place given, as the  number
       of  seconds  since  00:00:00  GMT,  Jan.  1, 1970, with an
       optional decimal extension, in order to make times unique.
       Note  that  slapd  does  not make times unique, but slurpd
       makes all times unique in its copies of the replog  files.

            time: <integer[.integer]>

       Next, the distinguished name of the entry being changed is
       given:

            dn: <distinguishedname>

       Next, the type of change being made is given:

            changetype: <[modify|add|delete|modrdn]>

       Finally, the change information itself is given, the  for­
       mat  of which depends on what kind of change was specified
       above.  For a changetype of modify, the format is  one  or
       more of the following:

            add: <attributetype>
            <attributetype>: <value1>
            <attributetype>: <value2>
            ...
            -

       Or, for a replace modification:

            replace: <attributetype>
            <attributetype>: <value1>
            <attributetype>: <value2>

       For a changetype of add, the format is:

            <attributetype1>: <value1>
            <attributetype1>: <value2>
            ...
            <attributetypeN>: <value1>
            <attributetypeN>: <value2>

       For a changetype of modrdn, the format is:

            newrdn: <newrdn>
            deleteoldrdn: 0 | 1

       where a value of 1 for deleteoldrdn means  to  delete  the
       values  forming the old rdn from the entry, and a value of
       0  means  to  leave  the   values   as   non-distinguished
       attributes in the entry.

       For  a  changetype of delete, no additional information is
       needed in the record.

       The format of the values is the LDAP Directory Interchange
       Format described in ldif(5).

       Access  to  the  slapd.replog file is synchronized through
       the use of flock(3) on the  file  slapd.replog.lock.   Any
       process  reading  or  writing  this  file should obey this
       locking convention.


EXAMPLE

       The following sample slapd.replog file  contains  informa­
       tion on one of each type of change.

            replica: truelies.rs.itd.umich.edu
            replica: judgmentday.rs.itd.umich.edu
            time: 797612941
            dn: cn=Babs Jensen,dc=example,dc=com
            changetype: add
            objectclass: person
            cn: babs
            cn: babs jensen
            sn: jensen

            replica: truelies.rs.itd.umich.edu
            replica: judgmentday.rs.itd.umich.edu
            time: 797612973
            dn: cn=Babs Jensen,dc=example,dc=com
            changetype: modify
            add: description
            description: the fabulous babs

            replica: truelies.rs.itd.umich.edu


SEE ALSO

       ldap(3), ldif(5), slapd(8), slurpd(8)


ACKNOWLEDGEMENTS

       OpenLDAP  is developed and maintained by The OpenLDAP Pro­
       ject (http://www.openldap.org/).  OpenLDAP is derived from
       University of Michigan LDAP 3.3 Release.

OpenLDAP 2.1.22             06-26-2003            SLAPD.REPLOG(5)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =


  




Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.04 Seconds