s3: Optimize g_lock_lock for a heavily contended case
[Samba.git] / source4 / setup / share.ldif
blob750a070c8a8354d558f9ef6ca74dc621fc49d229
1 dn: @INDEXLIST
2 @IDXATTR: name
4 dn: @ATTRIBUTES
5 cn: CASE_INSENSITIVE
6 dc: CASE_INSENSITIVE
7 name: CASE_INSENSITIVE
8 dn: CASE_INSENSITIVE
9 objectClass: CASE_INSENSITIVE
11 ### Shares basedn
12 dn: CN=Shares
13 objectClass: top
14 objectClass: organizationalUnit
15 cn: Shares
17 ### Default IPC$ Share
18 dn: CN=IPC$,CN=Shares
19 objectClass: top
20 objectClass: share
21 cn: IPC$
22 name: IPC$
23 type: IPC
24 path: /tmp
25 comment: Remote IPC
26 max-connections: -1
27 available: True
28 readonly: True
29 browseable: False
30 ntvfs-handler: default
32 ### Default ADMIN$ Share
33 dn: CN=ADMIN$,CN=Shares
34 objectClass: top
35 objectClass: share
36 cn: ADMIN$
37 name: ADMIN$
38 type: DISK
39 path: /tmp
40 comment: Remote Admin
41 max-connections: -1
42 available: True
43 readonly: True
44 browseable: False
45 ntvfs-handler: default