You should be able to use ldapmodify's continuous operation mode (-c
option). This will report errors, but continue performing the
operations listed in your file. The default behavior is to exit on an
error condition.
-NGK
Ben Steeves wrote:
On 7/25/05, Alastair Neil <ajneil(a)gmail.com> wrote:
>Thanks, I see I was being dense. :)
>
>
>
The eduPerson schema file you were trying to use tries to delete the
objectclass and attributetypes associated with eduPerson before
re-creating them (I suppose it does this in case you are "upgrading"
from a previous version). The problem is that FDS doesn't like
deleting schema objects that aren't there to begin with. SunOne 5.1
didn't have a problem doing that, the same schema file applied cleanly
just using an ldapmodify command.
I assume it's a setting somewhere that's been switched at some point.