Chris Ridd wrote:
On 17/11/04 10:44 am, Joerg Delker <[EMAIL PROTECTED]> wrote:
The latter could be avoided by doing a base64 encode on the attribute value.
I don't know if a) was fixed, yet!?
There's a change in r439 on LDIF.pm which alters the re matching attribute
names. Does that revisi
On 17/11/04 10:44 am, Joerg Delker <[EMAIL PROTECTED]> wrote:
> I would bet, it's that
>
> attr: something
>
> "bug" (#7868) again, being parsed as an import URL.
>
> If I remeber correctly we figured that this is
> a) a parsing bug in perl-ldap (treating "attr: <" as "attr:<"), *and*
> b
Graham Barr wrote:
On Mon, November 15, 2004 5:49 am, ¼Û»óÁØ said:
$entry = $inldif->read_entry(); is Line 32.
ldif data size is 1.1Gbyte
Well obvioulsy don't send all that :-) But if you can identify the entry
being read at the time of the error, it would help us help you if we can
see it.
On Mon, November 15, 2004 5:49 am, ¼Û»óÁØ said:
> $entry = $inldif->read_entry(); is Line 32.
>
> ldif data size is 1.1Gbyte
Well obvioulsy don't send all that :-) But if you can identify the entry
being read at the time of the error, it would help us help you if we can
see it.
Graham.
$entry = $inldif->read_entry(); is Line 32.
ldif data size is 1.1Gbyte
why this error occurs? help me?
unix system is AIX 5.2.
