Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (nike.apache.org: domain of camilleri.jon@gmail.com
 designates 72.14.220.154 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:content-type;
        b=QTvJfcvRDkncILxNat2eV4O2l9N/1gzRjYBo4P919RSPJqFq+P4/ZJxFwmJDFVy5US
         BTfpexJgzMgoZ/rw6S+cUpAYDFHGQJvGxmX8l/zBEyXyMWpeRy7i3AQX+EWgpaZWC4bs
         wGtbQ0sg8EE08+8RQYW+gKmBUq+Bk/bGKHokw=
MIME-Version: 1.0
Reply-To: camilleri.jon@gmail.com
In-Reply-To: <4A4F5D3D.6010906@nextury.com>
References: <3c5d272e0907040458p540fb77bv23b95329004a417@mail.gmail.com>
	 <4A4F5AF3.9000302@PingToo.com> <4A4F5D3D.6010906@nextury.com>
Date: Sat, 4 Jul 2009 17:26:25 +0200
Message-ID: <3c5d272e0907040826h3616aaah2222a0f140172247@mail.gmail.com>
Subject: Re: invalid .ldif? [newbie]
From: Jonathan Camilleri <camilleri.jon@gmail.com>
To: users@directory.apache.org
Content-Type: multipart/alternative; boundary=000e0cd2518c64fdaa046de2e58a

--000e0cd2518c64fdaa046de2e58a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Well, it seems to me that lines 8/9 do not start off with a space, although
Burch wrote that they should be .  Apache Directory Studio seemed to point
out issues in that part, so I'm thinking that the parser "did not like" the
spacing there, is this so?


http://pastebin.com/m7b7788e7

2009/7/4 Emmanuel Lecharny <elecharny@apache.org>

> Brian Burch wrote:
>
>> Jonathan Camilleri wrote:
>>
>>> I've just loaded an .ldif file within Apache Directory Studio and the
>>> program is pointing out /Unexpected token/.  I can't see anything wrong=
 with
>>> the file, any ideas pls?
>>>
>>
>> Don't know about apache studio, but I've often had this sort of error wi=
th
>> command line ldapmodify when I've copied a windoze or os2 based ldif fil=
e to
>> unix and then updated it there. In almost every case, I've tracked it do=
wn
>> to a cr/lf problem.
>>
> Unlikely ...
>
> Otherwise, there are many potential traps :
>
> * no space after the ':' or '::'
> * a  multi-line value not starting with a space
> * an attribute type with a non valid char in it
> * a missing ':'
> * a missing RC at the end of the file (not sure if it still generates an
> error...)
> * the #version:1 does not contain the valid '1' number
>
> Without the file, it's hard to say ...
>
>
>> If this is possible in your case, edit the file under linux; go to EVERY
>> single end-of-line position and delete characters until the next line
>> concatenates with the current one; hit return. (repeat for every line,
>> including the last empty line).
>>
> A trick on linux/unix, to remove window$ ^M : open your file in vi, and
> type :%s/^V^M// in command mode
> (to produce the ^V, just hit the control key and the V key. The very same
> for ^M). Doing the same with sed should also work...
>
>
>
> --
> --
> cordialement, regards,
> Emmanuel L=C3=A9charny
> www.iktek.com
> directory.apache.org
>
>
>


--=20
Jonathan Camilleri

Mobile (MT): 00356 7982 7113
E-mail: camilleri.jon@gmail.com
Please consider your environmental responsibility before printing this
e-mail.

I usually reply to e-mails within 2 business days.  If it's urgent, give me
a call.

--000e0cd2518c64fdaa046de2e58a--