Jim Summers wrote: > Hello All, > > I was modifying the value of an attribute, automountInformation in > this instance. The modify works as expected, but when I use > ldapsearch to dump the entry containing the new value it seems to > truncate it at 78 characters, that is (attribute name + attribute > value). The remainder of the value is on the next line, which has > caused some scripts to not work as expected. > > The manpage for ldapsearch did not reveal any clues or switches to get > around this length limit. Could it be a server limit? > > Interesting also is that db2ldif produces the same behavior. This is part of the LDIF standard. You can refer RFC 2849 for details on the LDIF syntax. > > Ideas on what I could do to get the value retruned back on one line? The "-U" option to db2ldif will tell it to not fold lines. The "-T" option to ldapsearch will do the same. -NGK > > STRANGE EXAMPLE OUTPUT: > =============== > automountInformation: -rw,actimeo=30,rsize=32768,wsize=32768 > fs001:/raid/facst > aff/faharris > =============== > > EXPECTED OUTPUT: > =============== > automountInformation: -rw,actimeo=30,rsize=32768,wsize=32768 > fs001:/raid/facstaff/faharris > =============== > > The above examples may not be clear due to email wrapping, but in the > first one ldapsearch truncates at the "t" and in the second there is > not truncating. > > TIA
