--On Wednesday, December 06, 2006 2:15 PM -0500
[EMAIL PROTECTED] wrote:
Quoting Quanah Gibson-Mount <[EMAIL PROTECTED]>:
--On Wednesday, December 06, 2006 9:48 AM -0500
[EMAIL PROTECTED] wrote:
Ok.
Fixed my slapd.conf. Here is what I get with each entry from slapadd-c
-l
slapadd:dn="uid=droggie,ou=people,dc=harrisonburg,dc=k12,dc=va,dc=us"(l
in e=20419): (65) invalid structural object class chain(account/person)
slapadd -d1 -l str2entry: entry -1 has multiple
DNs"uid=dnuckoles,ou=people,dc=harrisonburg,dc=k12,dc=va,dc=us"
and"uid=bkurtz,ou=people,dc=harrisonburg,dc=k12,dc=va,dc=us"
Well, that makes perfect sense. An entry can have one, and only one,
structural object Class. You need to decide if your entries are person
or account structurally.
I finally got the .ldif file to import. I removed the object class
person entry from each account, then removed the space that created.
Usernames and accounts transferred, but no passwords or email accounts.
I get attribute 'sn' not allowed. Weird thing though, one persons
account transferred completely. Can I safely remove the attribute sn
from the file?
"sn" stands for surname, i.e., the user's last name. Does anything you run
use sn? I have no idea whether or not you can remove it, it depends on
your data usage. ;)
You may want to read over:
<http://www.stanford.edu/services/directory/trees/>
to see one possibility for handling the differences between people and
accounts.
--Quanah
--
Quanah Gibson-Mount
Principal Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
---
You are currently subscribed to ldap@umich.edu as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
