Re: IMHO incorrect info in the documentation

[Alexei Monastyrnyi <alexeim@orcsoftware.com>]

Hi Kurt.

A bit strange reply...

I can see that what documentation has is different from what the real 
life has.
My intention was just to draw ones attention to this inconsistence.
People read the documentation, supposing that it reflects real things.

What is it about? "Go there, do that...". A sort of bureaucratic machine 
in OpenLDAP project? :-)

Sorry if it was sharper than needed.

A.

PS
And people usually say "hello" in the beginning... didn't you learn that 
as school?

info+1095165085@OpenLDAP.org wrote:

> If you believe there to be a documentation bug, you should
> report it by filing a report in the OpenLDAP Issue Tracking
> System <http://www.openldap.org/its/>.  If you are not sure,
> you should likely raise a discussion on the openldap-bugs
> or openldap-software mailing list prior to filing the report.
>
> Regards, Kurt
>
> At 05:35 AM 9/14/2004, Alexei Monastyrnyi wrote:
>  
>
> > Hi.
> > Maybe I'm wrong, but...
> >
> > In this section of Admin Guide you mention of files containing slurpd log, rejection etc.
> >
> >
> >   13.5.1. Replication errors
> >
> > When slurpd propagates a change to a slave slapd and receives an error return code, it writes the reason for the error and the replication record to a reject file. The reject file is located in the same directory as the per-replica replication logfile, and has the same name, but with the string ".rej" appended. For example, for a replica running on host slave.example.com, port 389, the reject file, if it exists, will be named
> >
> >     /usr/local/var/openldap/replog.slave.example.com:389.rej
> >
> >
> > By default slurpd generates the following files in a different directory. At least slurpd from 2.2.15 (considered as STABLE) does so...
> >
> > alien:alexeim> ls -l /usr/local/var/openldap-slurp/replica
> > total 1284
> > -rw-rw----   1 root     staff     644734 Sep 14 00:17 ra.orcsoftware.com:389.rej
> > -rw-rw----   1 root     staff          0 Sep 14 00:17 ra.orcsoftware.com:389.rej.lock
> > -rw-rw----   1 root     staff        962 Sep 14 00:22 slurpd.replog
> > -rw-rw----   1 root     staff          0 Sep 14 00:22 slurpd.replog.lock
> > -rw-rw----   1 root     staff         36 Sep 14 00:17 slurpd.status
> > -rw-rw----   1 root     staff          0 Sep 14 00:16 slurpd.status.lock
> >
> > Cheers,
> > Alexei.
> >
> >
> >
> > OpenLDAP Foundation wrote:
> >
> >    
> >
> > > *********************
> > > * Automated message *
> > > *********************
> > >
> > > The mailbox <info@OpenLDAP.org> requires keyed access.
> > >
> > > You may use the temporary address <info+1095165085@OpenLDAP.org>
> > > to deliver e-mail to this box.  No solicitations,
> > > please.  This temporary keyed address will expire
> > > in two weeks.
> > >
> > > *********************
> > >
> > > Note:
> > >
> > > Replies to this message will be forwarded to our volunteer
> > > staff who will respond to your message within a reasonable
> > > amount of time.  Normally 3-5 days.
> > >
> > > The OpenLDAP FAQ provides information regarding LDAP in
> > > general as well as OpenLDAP Software.
> > >       http://www.openldap.org/faq/
> > >
> > > OpenLDAP Software is user supported.  Questions regarding
> > > the use of OpenLDAP Software can be directed to the
> > > <openldap-software@openldap.org> mailing list.  General
> > > LDAP questions should be directed to the U-Mich LDAP
> > > <ldap@umich.edu> mailing list.  For information regarding
> > > these lists, including list charters, policies, and
> > > subscription information, see:
> > >       http://www.openldap.org/lists/
> > >
> > > Please review list archives before posting.
> > >
> > > Issues (bugs, enhancement requests) with OpenLDAP Software,
> > > documentation, web site, etc., should be reported using the
> > > OpenLDAP Issue Tracking System.
> > >       http://www.openldap.org/its/
> > >
> > >
> > >
> > >
> > >      
>
>
>