Using BSD Configuration Files in Directory Access

[Cpt.Tylor]

I work in a university environment, and one of our goals for adding OS X clients to the network is to treat them like UNIX machines. All UNIX machines on the network are pushed the necessary flat files (passwd, host, etc.) each night. Setting up each OS X client to accept these files and use them is ideal because the infrastructure is already in place, and it works well. So, my problem is that although Apple provides a plugin for Open Directory that allows the machine to get authentication data from the /etc flat files, I have not been able to get it to work. The files are in the correct format, but when a user attempts to log in, they are denied because the system hasn’t parsed the files. Help!

[Cpt.Tylor]

I have it set up to use a custom path with the first node being /NetInfo/root and the second being /BSD Configuration Files/Local

[stevebrowne]

Install Developer Tools – apparently this provides the necessary plist reader tools.

[Cpt.Tylor]

The developer tools were installed from the beginning…this really baffles me.

[rrdionne]

Is there a way to add the bsd files to the search path in the command line?

Thanks,
+R

[rrdionne]

Looks like this does it:

dscl /Search -create / SearchPolicy CSPSearchPath
dscl /Search -append / CSPSearchPath /BSD/local

+R

[Author]

Posts