1smbautohome(4)                   File Formats                   smbautohome(4)
2
3
4

NAME

6       smbautohome - CIFS autohome configuration
7

SYNOPSIS

9       smbautohome
10
11

DESCRIPTION

13       The  Solaris CIFS service can automatically share home directories when
14       a CIFS client connects. The autohome map file,  /etc/smbautohome,  uses
15       the  search  options  and  rules  to  determine whether to share a home
16       directory when a CIFS client connects to the server.
17
18
19       For example, the following entries specify the  autohome  rules  for  a
20       particular environment:
21
22         +nsswitch     dn=ad,dn=sun,dn=com,ou=users
23         jane    /home/?/&    dn=ad,dn=sun,dn=com,ou=users
24
25
26
27
28       The  nsswitch  autohome entry uses the naming service to match users to
29       home directories. The second autohome entry  specifies  that  the  home
30       directory for user jane is /home/j/jane.
31
32   autohome Map Entry Format
33       A map entry, which is also referred to as a mapping, uses the following
34       format:
35
36         key location [ options ]
37
38
39
40
41       key is a user name, location is the fully qualified path for the user's
42       home  directory,  and options specifies the share options, for example,
43       an AD container or description. See  sharemgr(1M)  for  information  on
44       share options.
45
46
47       If  you  intend to publish the share in Active Directory (AD), you must
48       specify an AD container name, which is specified as  a  comma-separated
49       list of attribute name-value pairs. The attributes use the LDAP distin‐
50       guished name (DN) or relative distinguished name (RDN) format.
51
52
53       The DN or RDN must be specified in LDAP format by using  the  following
54       attribute types:
55
56           o      cn= represents the common name
57
58           o      ou= represents the organizational unit
59
60           o      dc= represents the domain component
61
62
63       The attribute type that is used to describe an object's RDN is called a
64       naming attribute. AD uses the naming attributes as follows:
65
66           o      cn for the user object class
67
68           o      ou for the OU (organizational unit) object class
69
70           o      dc for the domainDns object class
71
72   autohome Map Key Substitution
73       The autohome feature supports the following wildcard substitutions  for
74       the value of the key field:
75
76           o      The  ampersand character (&) is expanded to the value of the
77                  key field for the entry in which it occurs. In the following
78                  example, & expands to jane:
79
80                    jane /home/&
81
82
83           o      The  question mark character (?) is expanded to the value of
84                  the first character in the key field for the entry in  which
85                  it occurs. In the following example, ? expands to j:
86
87                    jane /home/?/&
88
89
90   Wildcard Rule
91       When  supplied  in  the key field, the asterisk character (*) is recog‐
92       nized as the "catch-all" entry. Such an entry matches any key not  pre‐
93       viously matched.
94
95
96       For example, the following entry would map any user to a home directory
97       in /home in which the home directory name was  the  same  as  the  user
98       name:
99
100         *    /home/&
101
102
103
104       The wildcard rule is only applied if an appropriate rule is not matched
105       by another map entry.
106
107   NSSwitch Map
108       The nsswitch map is used to request that the home directory be obtained
109       from  a  password database, such as the local, NIS, NIS+, or LDAP data‐
110       bases. If an AD path is appended, it is used to publish shares.
111
112         +nsswitch
113
114
115
116       Like the "catch-all" entry, the nsswitch map is  only  searched  if  an
117       appropriate rule is not matched by another map entry.
118
119
120       The  wildcard and nsswitch rules are mutually exclusive. Do not include
121       an nsswitch rule if a wildcard rule has already been defined.
122

FILES

124       /etc/smbautohome
125

ATTRIBUTES

127       See the attributes(5)  man  page  for  descriptions  of  the  following
128       attributes:
129
130
131
132
133       ┌─────────────────────────────┬─────────────────────────────┐
134       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
135       ├─────────────────────────────┼─────────────────────────────┤
136       │Availability                 │SUNWsmbsu                    │
137       ├─────────────────────────────┼─────────────────────────────┤
138       │Interface Stability          │Uncommitted                  │
139       └─────────────────────────────┴─────────────────────────────┘
140

SEE ALSO

142       sharectl(1M),  sharemgr(1M), smbadm(1M), smbd(1M), smbstat(1M), smb(4),
143       attributes(5)
144
145
146
147SunOS 5.11                        5 Jan 2009                    smbautohome(4)
Impressum