Re: Object Class Violation

I think it would be much better to just support samba 3 since samba 3 is
widely deployed and distributed now.  There's no point in catering to
samba 2 users now.

Someone I think either provided patches or branched DA for that exactly.
Can't remember.

El mar, 02-08-2005 a las 17:14 -0700, Neil Schneider escribi=C3=B3:
> Mike Jackson said:
> > Neil Schneider wrote:
> >
> >>
> >> My primary objection to the way that DA works, is it makes
> >> assumption
> >> what I require, without first asking me if it's true. If it asked,
> >> during the setup or had a preference dialog, where I could make
> >> choices about which attributes I require, that would be much better.
> >>
> >> The problem seems to stem from a conflict between objectclass
> >> account
> >> and objectclass inetOrganizationalPerson. They are both structural
> >> classes, and as such cannot both be included.
> >
> >
> > Right, the decision whether to add "host" attribute or not is
> > triggered
> > by the wizard when adding a new user:
> >
> >
> > 	"Grant access to all computers in the network"
> >
> >
> > Leave this checked, and there should be no problem. Uncheck it, and DA
> > tries to add the "host" attribute and "account" object class to
> > entries.
> > Or are you seeing a different behaviour?
>=20
> I'm missing something. It would be great if all the required fields
> were marked, since I always seem to have difficulty getting diradmin
> to work. I'm still get ObjectClass violations, when I try to create an
> account from scratch. Unchecking "Grant access to all computers in the
> network" solved the problem. So I conclude, if you "Grant access to
> all computers in the network" then DA trys to use both InetOrgPerson
> and account at the same time. They are both StructuralObjectClasses
> and therefore an error.
>=20
> Also the schema for samba is outdated, according to what I'm seeing.
> The smbHome attribute is deprecated in Samba3. The new attribute is
> "sambaHomePath". So it appears that DA is not compatible with samba3.
>=20
> Is there no way to add the capability to check against the schema
> chosen to make sure all the attributes DA expects are present, and
> then let the admin know?
>=20
--=20
                Rudd-O          <[email protected]>
                http://www.amautacorp.com/staff/Rudd-O/