| Title: | PATHWORKS for OSF/1 |
| Notice: | see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX |
| Moderator: | CPEEDY::LONG |
| Created: | Thu Apr 22 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1874 |
| Total number of notes: | 6870 |
Hi,
Could anybody please tell me in simple terms what each of the files in
the /usr/net/servers/lanman/datafiles are used for and in what way they
are linked to each other and any relation to the ../samsave files they
have when trying to run ../bin/samcheck -s / -r ect.
Also it there is any any way of re-creating the accounts database for
the v6 server as per there is a start article using buildacc to
re-create a corrupt v5 database.
Trevor Burns UK CSC who is starting to see a few funnies with some
"coruption" in large user databases.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1855.1 | Quick overview of datafiles | CPEEDY::VATNE | Peter Vatne, Advanced Server for Digital Unix Engineering | Wed May 14 1997 15:46 | 19 |
/usr/net/servers/lanman/datafiles/ Builtin - SAM database records for "built-in" accounts LongName - ASCII name of server Name - ASCII short name of server acl - ACL database chglog.lmx - SAM database replication records lsa - SAM database mapuname records prototype - ASCII prototype of kit inventory /usr/net/servers/lanman/domains/ <domainname> - SAM database records for user and group accounts. The filename of the SAM database is the domain name. When a samcheck -r (repair database) command is done, the SAM database blob files are first copied to the samsave directory. That way you can always get back to your original configuration by hand-restoring those files and restarting the server. | |||||
| 1855.2 | samcheck -r | CPEEDY::VATNE | Peter Vatne, Advanced Server for Digital Unix Engineering | Wed May 14 1997 15:50 | 8 |
To answer the second part of your question, samcheck -r is the only tool I know of to fix up a broken SAM database. If that doesn't work, then your only recourse is to re-install and re-initialized the SAM database. Unfortunately, this means all the user accounts will have new SIDs, and therefore all permissions must be reapplied to all files and directories. Please report all instances of database corruption, even ones that samcheck -r was able to repair. | |||||