Leopard server DHCP static map file location?

Question

Level 1

21 points

Leopard server DHCP static map file location?

Hi,
My XServe G5 (10.5.6) fails to boot, I can't get Retrospect 6.1 to recognise my LTO3 drive and I need to backup my configuration files before I reformat and reinstall.
Where are the files now located that configure the static maps? This is the single most important configuration file for me. I want to copy it to the external hard drive I am using to run the server at the moment to get my network up and running as usual rather than via my emergency system which does not allow static maps.

Xserve G5, Mac OS X (10.5.6)

Posted on Jun 1, 2009 7:35 AM

Reply

Answer 1

Best reply

Gordon Davisson

Level 3

520 points

Jun 1, 2009 11:05 PM in response to Grant Wray

The static maps should be recorded in computer records in one of the server's directory domains; the slightly tricky question is, which directory domain?

• If the server isn't set up as an Open Directory master (or replica), it'll only have one domain: the default local domain, and its computer records will be stored as .plist files in /private/var/db/dslocal/nodes/Default/computers/

• If the server is an OD master (or replica), the records might be either there, or in the OD network domain, in which case they're buried in a Berkeley database in /private/var/db/openldap/openldap-data/.

If they're in the openLDAP database, I don't know any terribly clean way to extract them from the rest of the directory data; hopefully they're in dslocal instead, in which case you can just copy them into the corresponding directory on a new server and have them take effect (though you may have to reboot to get it to notice them).

Reply

Answer 2

Jun 2, 2009 9:10 AM in response to Grant Wray

If the server is an OD master (or replica), the records might be either there, or in the OD network domain, in which case they're buried in a Berkeley database in /private/var/db/openldap/openldap-data/.

The records will be in both places on an OD master. They could have been exported as LDIF files prior to your disk failure.

The only tools that I currently know of that could possibly be of assistance in exporting your database in off-line mode would be from the OpenDS project. Since you would need another Mac to install this on and a lot of fiddling to get the database files in the right place to export, this might be more trouble than it's worth.

Reply